-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
feat(baseapp): expose Mempool
#17954
Conversation
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.
ACK but curious about your use case.
Additionally, can you add a changelog under unreleased improvements? This is something we can backport all the way down to v0.47.
Second @julienrbrt's question. What's the exact use-case (not that I'm against it). Given that the app sets the mempool, you should have access to it at some point in the stack, no? |
we have to set the client context from the server on our mempool. Just prevents from having to store another pointer to it on our app. |
nothing wild haha |
👍🏾—Can we still get a changelog? :) |
I'll add the changelog in the backport of v0.47. |
Description
Closes: #XXXX
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
make lint
andmake test
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change