docs: surface 'timestamp' in Transaction Context for search#408
Conversation
The new Transaction Context page used 'datetime' in headings and 'timestamp' only in code/body, so searching the docs site for 'timestamp' (the term most devs reach for) ranked the page poorly or missed it entirely. - Mention 'timestamp' explicitly in the page intro. - Rename '## Time in a contract' to '## Time and Timestamps'. - Add '### Transaction Timestamp' heading with a small table covering the three forms (Unix seconds, datetime object, ISO string).
✅ Deploy Preview for genlayer-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Summary
Follow-up to #407. The new Transaction Context page used 'datetime' in its headings and 'timestamp' only inside code blocks / body text, so searching the docs site for 'timestamp' — the term most devs actually type — didn't surface this page.
## Time in a contract→## Time and Timestamps.### Transaction Timestampheading with a small table covering the three forms (Unix seconds, datetime object, ISO string).Background
Nextra 2's built-in search is FlexSearch-based and indexes page content with stronger weights for the title and headings. There is no tag/keyword/synonym system, so the only lever is making the search terms actually appear in headings and the intro paragraph.
Test plan
pnpm dev, search "timestamp" in the docs sidebar, confirm Transaction Context appears as a top result