feat: payload type assertions #1395
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hi @yknl, created some type assertions that may be helpful. Was looking to use them in intercepted requests in our integration tests for the Hiro Wallet. Let me know if you'd like them added here. Not sure if the I should update the changelong too, or that's something you automate? |
|
Thanks 🙏🏻 |
|
Wonderful addition thanks 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds type assertions for the various payload types.
Type of Change
Does this introduce a breaking change?
No
Are documentation updates required?
No
Testing information
Testing doesn't seem necessary for type assertions.
Checklist
npm run testpasses