Conversation
Contributor
|
Warning Rate limit exceeded
⌛ 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. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (6)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughAdds a new TypeScript type and a React Query options function to fetch vesting-delegation expirations for a given account; also re-exports the new type and query option from the module index files. Changes
Sequence Diagram(s)sequenceDiagram
participant Consumer
participant ReactQuery as React Query
participant SDK as SDK (query fn)
participant Hive as Hive DB API
Consumer->>ReactQuery: useQuery(getVestingDelegationExpirationsQueryOptions(username))
ReactQuery->>SDK: invoke queryFn (if enabled)
SDK->>Hive: CONFIG.hiveClient.database_api.find_vesting_delegation_expirations({ account: username })
Hive-->>SDK: { delegations: [...] }
SDK-->>ReactQuery: return delegations
ReactQuery-->>Consumer: provide data / loading / error
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In
`@packages/sdk/src/modules/wallet/queries/get-vesting-delegation-expirations-query-options.ts`:
- Around line 17-28: getVestingDelegationExpirationsQueryOptions must guard
against undefined username to avoid calling CONFIG.hiveClient.call with {
account: undefined } (which bypasses enabled when using direct
queryClient.fetchQuery/prefetchQuery). Modify
getVestingDelegationExpirationsQueryOptions to check if username is falsy at the
top and return a safe queryOptions object (e.g., enabled: false and a no-op
queryFn that returns an empty array) instead of proceeding to call
CONFIG.hiveClient.call("database_api","find_vesting_delegation_expirations", {
account: username }); this ensures functions like queryClient.fetchQuery won't
make an invalid RPC when username is absent.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 3ea7c624-23c2-473c-bec4-164aca859cc5
⛔ Files ignored due to path filters (7)
packages/sdk/dist/browser/index.d.tsis excluded by!**/dist/**packages/sdk/dist/browser/index.jsis excluded by!**/dist/**packages/sdk/dist/browser/index.js.mapis excluded by!**/dist/**,!**/*.mappackages/sdk/dist/node/index.cjsis excluded by!**/dist/**packages/sdk/dist/node/index.cjs.mapis excluded by!**/dist/**,!**/*.mappackages/sdk/dist/node/index.mjsis excluded by!**/dist/**packages/sdk/dist/node/index.mjs.mapis excluded by!**/dist/**,!**/*.map
📒 Files selected for processing (4)
packages/sdk/src/modules/wallet/queries/get-vesting-delegation-expirations-query-options.tspackages/sdk/src/modules/wallet/queries/index.tspackages/sdk/src/modules/wallet/types/index.tspackages/sdk/src/modules/wallet/types/vesting-delegation-expiration.ts
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/web/src/app/`(staticPages)/terms-of-service/page.tsx:
- Around line 548-550: Replace the general inbox email shown in the Terms of
Service page where the "Child Safety Point of Contact" is rendered (the text
containing "<code>hello@ecency.com</code>") with the dedicated, restricted
child-safety intake alias owned by trust-and-safety/legal; locate the string in
page.tsx (the terms-of-service page component) and update the <code>...</code>
value to the new address, ensuring any display and copyable markup continues to
use the <code>...</code> element and no other text is changed.
- Around line 562-565: Update the "27. Digital Services Act (EU) Redress
Options" block in the terms-of-service page component to include an actionable
entry point for moderation appeals: add a sentence with a direct link to the
internal moderation appeal form or support route (e.g.,
"/support/moderation-appeal" or the existing support page) and a contact address
(e.g., moderation@ecency.example) so users know how to submit an internal
review; also include a link to the certified out-of-court dispute settlement
body (Article 21) for EU users. Locate the JSX block containing the <h2> "27.
Digital Services Act (EU) Redress Options" in
apps/web/src/app/(staticPages)/terms-of-service/page.tsx and modify the
surrounding <p> elements to insert the form URL, email, and the external DSA
dispute body link.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: c495295b-7215-4263-aa37-7432167e95c2
📒 Files selected for processing (2)
apps/web/src/app/(staticPages)/terms-of-service/page.tsxpackages/sdk/src/modules/wallet/queries/get-vesting-delegation-expirations-query-options.ts
🚧 Files skipped from review as they are similar to previous changes (1)
- packages/sdk/src/modules/wallet/queries/get-vesting-delegation-expirations-query-options.ts
Comment on lines
548
to
550
| Child Safety Point of Contact: <code>hello@ecency.com</code>. To report suspected CSAM, | ||
| CSAE, or any threat to a minor related to Ecency, contact this address with links, | ||
| usernames, and supporting details so we can investigate and take action. |
Contributor
There was a problem hiding this comment.
Use a dedicated child-safety intake address instead of the general inbox.
hello@ecency.com is now the contact for CSAM/CSAE reports and Google Play child-safety notices. That is a sensitive workflow; it should go to a restricted alias owned by the trust-and-safety/legal process, not the general mailbox.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/web/src/app/`(staticPages)/terms-of-service/page.tsx around lines 548 -
550, Replace the general inbox email shown in the Terms of Service page where
the "Child Safety Point of Contact" is rendered (the text containing
"<code>hello@ecency.com</code>") with the dedicated, restricted child-safety
intake alias owned by trust-and-safety/legal; locate the string in page.tsx (the
terms-of-service page component) and update the <code>...</code> value to the
new address, ensuring any display and copyable markup continues to use the
<code>...</code> element and no other text is changed.
Comment on lines
+562
to
+565
| <h2>27. Digital Services Act (EU) Redress Options</h2> | ||
| <p>If you disagree with a content moderation decision made by Ecency, you may submit a complaint through available internal review or reporting mechanisms.</p> | ||
| <p>Users in the European Union may also refer disputes relating to moderation decisions to a certified out-of-court dispute settlement body in accordance with Article 21 of Regulation (EU) 2022/2065 (Digital Services Act).</p> | ||
| <p>Nothing in this section limits your right to seek judicial redress through the courts.</p> |
Contributor
There was a problem hiding this comment.
Make the DSA appeal path actionable.
This section says users can use internal review/reporting mechanisms, but it does not identify any route, form, or mailbox for moderation appeals. Please add a concrete entry point here so the redress flow is actually usable.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/web/src/app/`(staticPages)/terms-of-service/page.tsx around lines 562 -
565, Update the "27. Digital Services Act (EU) Redress Options" block in the
terms-of-service page component to include an actionable entry point for
moderation appeals: add a sentence with a direct link to the internal moderation
appeal form or support route (e.g., "/support/moderation-appeal" or the existing
support page) and a contact address (e.g., moderation@ecency.example) so users
know how to submit an internal review; also include a link to the certified
out-of-court dispute settlement body (Article 21) for EU users. Locate the JSX
block containing the <h2> "27. Digital Services Act (EU) Redress Options" in
apps/web/src/app/(staticPages)/terms-of-service/page.tsx and modify the
surrounding <p> elements to insert the form URL, email, and the external DSA
dispute body link.
feruzm
added
the
patch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary by CodeRabbit
New Features
Documentation