-
Notifications
You must be signed in to change notification settings - Fork 23
Contributor docs #562
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
base: main
Are you sure you want to change the base?
Contributor docs #562
Conversation
Co-authored-by: Manuel Montenegro <[email protected]>
✅ Deploy Preview for taco-nft-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for taco-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
||
3. User Context Management: | ||
|
||
They help manage user context, specifically the `:userAddress` parameter. This includes handling authentication tokens and ensuring that users are authenticated only once for multiple actions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also the :userAddressExternalEIP4361
context variable.
It also uses an auth provider for generating the AuthSignature - https://github.com/nucypher/taco-web/blob/main/packages/taco-auth/src/providers/external-eip4361.ts#L6.
Side note: my goal is to update the API via #560 in the next sprint.
[The below test](https://github.com/nucypher/taco-web/blob/b689493a37bec0b168f80f43347818095c3dd5ce/packages/taco/test/conditions/context.test.ts#L382C1-L429C6) demonstrates how a SIWE message can be reused for TACo authentication. | ||
This ensures that users don't have to sign multiple messages when logging into apps and decrypting TACo messages. | ||
|
||
```typescript |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this test in a test file somewhere already? Can we link to to test files/line numbers instead? That would ensure that the test always remains fresh. Some for other spots above.
Co-authored-by: Derek Pierre <[email protected]>
Looks like this needs a rebase, which will have conflicts. |
This is the same PR as #551. The previous PR was closed due to the destination branch being deleted.
Type of PR:
Required reviews:
Fixes https://github.com/nucypher/sprints/issues/27