Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add spotify urls to all episodes #1667

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

msmps
Copy link
Contributor

@msmps msmps commented Apr 28, 2024

Description

As part of some ongoing work here to bring syntax to the listeners fingertips via a Raycast extension...

I wanted to be able to launch each episode directly in the Spotify application. However, I soon realised this was not possible without the Spotify URI. This kicked off a weekend of work for me to figure out how to get the URI from Spotify for each of the episodes, given that there is currently no real relationship. I have written a tool (which I will link shortly for reference), to parse each markdown file and create a hashmap using the show date as the index and the episode/file information as the value. The tool then calls out to the Spotify API in batches to pull the episodes from Spotify and using the same show date, fetches the matching episode from the hashmap and updates the frontmatter of the markdown file.

I hope this is ok @wesbos @stolinski

Copy link

vercel bot commented Apr 28, 2024

@msmps is attempting to deploy a commit to the Syntax Team on Vercel.

A member of the Team first needs to authorize it.

@wesbos
Copy link
Collaborator

wesbos commented May 1, 2024

oh wow this is awesome! Ive wanted this all along! ill take a look at it shortly :)

@stolinski
Copy link
Collaborator

Wow this is awesome. Thank you @msmps

@w3cj
Copy link
Contributor

w3cj commented May 1, 2024

Thanks for working on this! Reviewing 765 changed files is quite a lot though.

Could you make a PR with only the schema / page updates, with maybe 1 markdown file updated for us to test and then link us your tool so we can add the links to the rest of the markdown files ourselves?

@msmps
Copy link
Contributor Author

msmps commented May 2, 2024

Thanks, folks! I appreciate the kind words! Of course, @w3cj, I've updated this pull request to only include the bare minimum for testing 😃 I'll upload my tool and return with a link! 👍 

@msmps
Copy link
Contributor Author

msmps commented May 3, 2024

Thanks for working on this! Reviewing 765 changed files is quite a lot though.

Could you make a PR with only the schema / page updates, with maybe 1 markdown file updated for us to test and then link us your tool so we can add the links to the rest of the markdown files ourselves?

I've pushed up the tool @w3cj; you can find it here! If you need any help with anything, feel free to connect with me on X or something! I look forward to getting these changes live! 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants