-
Notifications
You must be signed in to change notification settings - Fork 35
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
Allow other operations for tx search api #75
Conversation
Warning Rate limit exceeded@joon9823 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 8 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThe changes involve modifications to the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Manifest Files |
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.
Actionable comments posted: 2
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- src/client/lcd/api/TxAPI.ts (2 hunks)
Additional context used
Biome
src/client/lcd/api/TxAPI.ts
[error] 533-533: Avoid the delete operator which can impact performance.
Unsafe fix: Use an undefined assignment instead.
(lint/performance/noDelete)
Additional comments not posted (3)
src/client/lcd/api/TxAPI.ts (3)
189-189
: LGTM!The
TxSearchOp
type definition is correct and aligns with the PR objectives.
190-196
: LGTM!The updated
TxSearchOptions
interface correctly incorporates the newop
field, enhancing the flexibility of transaction searches.
532-532
: LGTM!The code correctly appends the query string to the
params
object.
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- src/client/lcd/api/TxAPI.ts (2 hunks)
Additional context used
Biome
src/client/lcd/api/TxAPI.ts
[error] 533-533: Avoid the delete operator which can impact performance.
Unsafe fix: Use an undefined assignment instead.
(lint/performance/noDelete)
Additional comments not posted (6)
src/client/lcd/api/TxAPI.ts (6)
189-190
: LGTM!The
TxSearchOp
type definition is correct and enhances the flexibility of the query options.
192-196
: LGTM!The
TxSearchOptions
interface update is correct and aligns with the newTxSearchOp
type definition.
524-530
: Add validation forkey
andvalue
fields.The
reduce
function correctly processes each query object, but it lacks validation for thekey
andvalue
fields. Consider adding validation to ensure they are not empty or invalid.Apply this diff to add validation:
const query: string = (options.query ?? []).reduce((str, q) => { + if (!q.key || !q.value) { + throw new Error('Invalid query: key and value must be provided') + } const op = q.op ?? '=' const value = q.key === 'tx.height' ? `${q.value}` : `'${q.value}'` const queryStr = op === 'EXISTS' ? `${q.key} ${op}` : `${q.key} ${op} ${value}` return str ? `${str} AND ${queryStr}` : queryStr }, '')
532-533
: Avoid using thedelete
operator.Using the
delete
operator can impact performance. Consider setting the property toundefined
instead.Apply this diff to avoid using the
delete
operator:if (query) params.append('query', query) -delete options['query'] +options['query'] = undefinedTools
Biome
[error] 533-533: Avoid the delete operator which can impact performance.
Unsafe fix: Use an undefined assignment instead.
(lint/performance/noDelete)
536-536
: LGTM!The loop correctly appends other options to the
params
object.
Line range hint
538-548
: LGTM!The return statement correctly processes the search result.
Tools
Biome
[error] 533-533: Avoid the delete operator which can impact performance.
Unsafe fix: Use an undefined assignment instead.
(lint/performance/noDelete)
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.
LGTM
the above tx search condition can be queried as below
Summary by CodeRabbit
New Features
Refactor