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

(Feature): Add command and functionality to parse/decode signed JWT in Web5 CLI #327

Open
7 tasks
Tracked by #322
blackgirlbytes opened this issue Aug 29, 2024 · 13 comments
Open
7 tasks
Tracked by #322

Comments

@blackgirlbytes
Copy link
Contributor

🚀 Goal

Add a new feature to the Web5 Rust CLI that allows users to parse or decode JSON Web Tokens (JWTs).

🔑 Tasks

  • Create a new command for parsing/decoding JWTs (e.g., web5 jwt decode)
  • Implement the logic to decode and display the header, payload, and signature of a JWT
  • Add options to format the output (e.g., pretty-print JSON)
  • Implement error handling for invalid JWTs
  • Add appropriate documentation to README for the new command
  • Write tests to ensure the feature works correctly
  • Update the CLI's help information to include the new command

🌟 Resources

⚡ Getting Started

  1. Comment ".take" on this issue to get assigned
  2. Fork the repository and create a new branch for this task
  3. Update the documentation as described in the tasks
  4. Submit a pull request with your changes
  5. Respond to any feedback during the review process

💭 Questions?

If you have any questions or need clarification, please comment on this issue or join our Discord community.
Happy coding! 🎉

@Marvellous111
Copy link

HECK YEAH.

.take

@blackgirlbytes
Copy link
Contributor Author

Hey hey @Marvellous111 . Thanks for your enthusiasm. This issue wont be available until Oct 1st for Hacktoberfest. Can you do the .take comment on that date and it will actually auto assign for you after that date? Thank you!

@Marvellous111
Copy link

Marvellous111 commented Sep 26, 2024 via email

@blackgirlbytes
Copy link
Contributor Author

hey @Marvellous111 . Are you still interested in this issue? If so, try commenting the keyword .take (not in the code ticks. Just doing this to avoid assigning the issue to me)

Thank you!

Copy link

github-actions bot commented Oct 2, 2024

Thanks for taking this issue! Let us know if you have any questions!

@Marvellous111
Copy link

.take

Copy link

github-actions bot commented Oct 2, 2024

The issue you are trying to assign to yourself is already assigned.

@Marvellous111
Copy link

hey @Marvellous111 . Are you still interested in this issue? If so, try commenting the keyword .take (not in the code ticks. Just doing this to avoid assigning the issue to me)

Thank you!

Hey, turns out it automatically assigned you?

Copy link

github-actions bot commented Oct 2, 2024

The issue you are trying to assign to yourself is already assigned.

@blackgirlbytes
Copy link
Contributor Author

lol i just manually assigned you @Marvellous111 i think it's cuz my comment still used the keyword but i thought putting it in backticks would stop it from assigning me.

@deauthe
Copy link

deauthe commented Oct 8, 2024

hey @Marvellous111 , Have you been working on this issue?

@Marvellous111
Copy link

Marvellous111 commented Oct 8, 2024 via email

@w3irdrobot
Copy link
Contributor

I can take this over the line if needed.

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

No branches or pull requests

4 participants