-
Notifications
You must be signed in to change notification settings - Fork 53
fix: types #304
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
Merged
Merged
fix: types #304
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
💡 Codebase verification
Update
torii.Query
type definition to includedont_include_hashed_keys
The property
dont_include_hashed_keys: true
is being used in several instances ofgetEventMessages
, but it is not defined in thetorii.Query
type. This inconsistency can lead to type errors and unexpected behaviors across the codebase.Action Items:
Update Type Definitions:
dont_include_hashed_keys?: boolean
to thetorii.Query
type to ensure it is recognized across all usages.Ensure Consistency:
getEventMessages
either include this property or handle its absence appropriately.Update Documentation:
dont_include_hashed_keys
in the JSDoc comments and any relevant documentation to inform users of its purpose and usage.Review Usage:
dont_include_hashed_keys
to ensure consistent behavior.Category:
🔗 Analysis chain
Update documentation and consider backwards compatibility for
dont_include_hashed_keys
The addition of
dont_include_hashed_keys: true
to thetoriiQuery
object modifies the behavior of the query sent to the Torii client. While this change may improve performance by reducing the amount of data returned, it raises several concerns:torii.Query
may need to be updated to include this new property.To address these issues, consider the following:
dont_include_hashed_keys
.torii.Query
type definition if necessary.To verify the impact of this change, we can search for other usages of
getEventMessages
in the codebase:This will help us understand if other parts of the codebase might be affected by this change.
[/run_scripts]
[/run_scripts]
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 84
Script:
Length of output: 5598
Script:
Length of output: 1374