-
Notifications
You must be signed in to change notification settings - Fork 1k
feat: add getRecentPrioritizationFees API #1233
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: add getRecentPrioritizationFees API #1233
Conversation
…forward an empty array to the RPC
steveluscher
left a comment
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.
| async getRecentPrioritizationFees( | ||
| publicKeys?: PublicKey[], | ||
| ): Promise<RecentPrioritizationFees[]> { | ||
| const keys = publicKeys ? publicKeys?.map(key => key.toBase58()) : []; |
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.
According to the spec, I think this should be undefined when:
- No keys were supplied.
- A zero-length array was supplied.
| }); | ||
|
|
||
| it('get recent prioritization fee', async () => { | ||
| if (mockServer) { |
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.
Usually we let these run in live mode, and just assert on the return values being numeric.
|
🎉 This PR is included in version 1.75.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |

Fixes #1095