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

Context type does not always have access to sender. #222

Open
jcblw opened this issue Oct 11, 2021 · 3 comments
Open

Context type does not always have access to sender. #222

jcblw opened this issue Oct 11, 2021 · 3 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@jcblw
Copy link
Contributor

jcblw commented Oct 11, 2021

If a function is passed to the context I would expect to be able to access all the values available in a context like sent. I think currently that function is only called once initial on startup of the api
@jcblw
Copy link
Contributor Author

jcblw commented Oct 11, 2021

Actually, it is called every query, it just does not have the sender every time.

@jcblw
Copy link
Contributor Author

jcblw commented Oct 11, 2021

Ok, looking at the code I think this may only be happening when we do a query from the background process.

@jcblw
Copy link
Contributor Author

jcblw commented Oct 12, 2021

Updating the title on this to be more specific to the bug.

@jcblw jcblw changed the title Unable to get sender in context function Context type does not always have access to sender. Oct 12, 2021
@jcblw jcblw added good first issue Good for newcomers bug Something isn't working labels Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working good first issue Good for newcomers
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jcblw