extensions
extensions copied to clipboard
Splitwise oauth
Description
Re-work of #10005 based on the updated codebase. Moves Splitwise to OAuth rather than manual API key configuration.
Checklist
- [x] I read the extension guidelines
- [x] I read the documentation about publishing
- [x] I ran
npm run buildand tested this distribution build in Raycast - [x] I checked that files in the
assetsfolder are used by the extension itself - [x] I checked that assets used by the
READMEare placed outside of themetadatafolder
Thank you for your contribution! :tada:
🔔 @maximilianzuern @DiogoFerrer @djpowers you might want to have a look.
Note for the Raycast team, this is not currently using a Raycast hosted PKCE proxy, it's using one I'm hosting that is a fork of the one from @mathieudutour. I'll start a discussion on Slack, but it would be great to solve PKCE proxying once and for all and make this self-service for the rest of the community.
I made a self-service proxy which you can access here: https://oauth.raycast.com/encrypt-form We haven't communicated about it because we still have to polish it a bit (the functionality isn't going to change so you can still use it)
@danpalmer Thank you for your contribution 🎉 LGTM!
@danpalmer would you be up for changing to @mathieudutour's self-hosted proxy 🙂
~~@pernielsentikaer id rather get a self service version up and running to end all the back and forth if that's possible. I happy to switch to a Raycast hosted version of that, but the constant back and forth of getting new instances spun up is a bit of a damper on development so it would be great to solve this in a more permanent way.~~
Edit: I should have read the preceding comment.
The link I mentioned above is a self-service version
Great, thanks for this, I'll get this updated soon.
This pull request has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊
This issue has been automatically closed due to inactivity.
Feel free to comment in the thread when you're ready to continue working on it 🙂
You can also catch us in Slack if you want to discuss this.