Skip to content

Conversation

@wibed
Copy link
Contributor

@wibed wibed commented Mar 12, 2024

i replaced some manual errors with normalized counterparts

wibed added 3 commits March 12, 2024 15:27
Signed-off-by: wibe <pbwo@pm.me>
Signed-off-by: wibe <pbwo@pm.me>
Copy link
Member

@0xTim 0xTim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this but it's a breaking change. I'm happy to roll it into a major release with the async/await changes but if we're going to do that we should remove the public enum altogether and replace it with static cases backed by an internal enum. See JWTError in JWTKit for reference

@wibed
Copy link
Contributor Author

wibed commented Mar 21, 2024

how does jwt kit map over imperial? could imperial be a thin wrapper and jwt-kit if it includes oauth tokens aswell?

@0xTim
Copy link
Member

0xTim commented Mar 25, 2024

It doesn't at all. The two are completely unrelated.

You could use a JWT once you've authenticated the user with Imperial but that's nothing to do with this library. The JWT link was only there as an example of how to get rid of a public enum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants