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.

Sign up for GitHub

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

Jump to bottom

Expose client token in state #296

Closed
picklelo opened this issue Jan 21, 2023 · 0 comments · Fixed by #316
Closed

Expose client token in state #296

picklelo opened this issue Jan 21, 2023 · 0 comments · Fixed by #316
Labels
enhancement Anything you want improved feature request A feature you wanted added to reflex
Milestone
v0.1.14

Comments

@picklelo
Copy link
Contributor

Sometimes the event handlers may need to know the specific client that is calling it, to do logic such as rate-limiting.

Each client has a token already, so we can just make this accessible in the state class as self.get_token()
@Alek99 Alek99 added feature request A feature you wanted added to reflex enhancement Anything you want improved labels Jan 21, 2023
@picklelo picklelo added this to the v0.1.14 milestone Jan 21, 2023
@Lendemor Lendemor mentioned this issue Jan 22, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Anything you want improved feature request A feature you wanted added to reflex
Projects
None yet
Milestone
v0.1.14
Development

Successfully merging a pull request may close this issue.

Add event token to router_data Lendemor/pynecone
2 participants
@picklelo @Alek99