docs: add FAQ about FBA event logs - #176
Conversation
Signed-off-by: Brendan Graetz <bguiz@users.noreply.github.com>
|
Warning Review limit reached
Next review available in: 23 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. 📝 WalkthroughWalkthroughThe Injective FAQ documentation file was reformatted to use consistent labeled Q/A blocks for existing address-conversion, infrastructure, and multicall3 entries. A new "Injective native modules" section was added explaining exchange-module event log visibility depending on execution context. ChangesFAQ Documentation Update
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Pull request overview
This PR improves the FAQ documentation by standardizing FAQ entries into labeled Q/A blocks and adding a new FAQ entry that explains why some Injective exchange-module event logs appear at the transaction level while others only appear at the block level (FBA context).
Changes:
- Reformatted existing FAQ items to use consistent
**Q**:/**A**:labeling. - Added a new “Injective native modules” FAQ entry describing transaction-level vs block-level event log emission and linking to relevant docs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.gitbook/faq.mdx:
- Around line 27-29: The FAQ answer text in the Injective address mapping
section is missing the hyphenated compound adjective; update the phrasing in the
markdown content to use “one-to-one” instead of “one to one” in the relevant Q&A
entry. Locate the sentence in the FAQ markdown near the address mapping answer
and make the wording consistent with standard compound adjective usage.
- Around line 73-91: Fix the grammar in the Injective native modules FAQ answer
by changing “an frequent batch auction (FBA) context” to “a frequent batch
auction (FBA) context” in the relevant FAQ entry. Update the prose in the
Injective exchange module explanation so the sentence reads naturally while
preserving the existing meaning and surrounding references to
MsgBatchUpdateOrders and EndBlocker.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Signed-off-by: Brendan Graetz <bguiz@users.noreply.github.com>
Summary by CodeRabbit