Format modifiers, Custom Format tokens - #64
Conversation
|
Warning Review limit reached
Next review available in: 38 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. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughTempo 3.10.0 adds localized format token modifiers and custom token evaluators, introduces plugin catalog synchronization and static catalog rendering, renames the finance namespace export, updates ticker plugin terminology, and refreshes package versions and documentation. ChangesFormatting extensions
Plugin catalog and 3.10.0 release
Estimated code review effort: 3 (Moderate) | ~30 minutes Sequence Diagram(s)sequenceDiagram
participant Tempo
participant Registry
participant Formatter
participant Evaluator
Tempo->>Registry: initialize registry.tokens
Registry->>Formatter: provide merged token definitions
Formatter->>Evaluator: evaluate custom token with ZonedDateTime and context
Evaluator-->>Formatter: return token output
Formatter-->>Tempo: return formatted string
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 `@packages/tempo/doc/1-getting-started/installation.md`:
- Around line 144-146: Update the TickerPlugin examples in
packages/tempo/doc/1-getting-started/installation.md (lines 144-146) and
packages/tempo/doc/8-project-and-support/releases/v3.x.md (lines 333-340) to
call Tempo.init({ license: 'YOUR_JWT_KEY' }) before Tempo.extend(TickerPlugin).
In `@packages/tempo/doc/3-extending-tempo/tempo.plugin.md`:
- Line 11: Update the “Naming Convention Standard” heading in the documentation
to use the expected ## level, preserving the surrounding heading hierarchy.
- Around line 11-17: Update the “Naming Convention Standard” section to
explicitly define the exported-symbol suffix for plugins built with
defineModule, ensuring it is consistent with the later defineModule examples and
the stated Module guidance. Keep the existing definePlugin, defineTerm, and
defineNamespace conventions unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: ff65ad36-ba4c-4e53-b891-5227bcfefd82
📒 Files selected for processing (32)
CHANGELOG.mdpackage.jsonpackages/library/package.jsonpackages/plugins/.bin/README.mdpackages/plugins/.bin/catalog-sync.mjspackages/plugins/.setup/catalog.jsonpackages/plugins/.setup/community-plugin-template.mdpackages/plugins/finance/README.mdpackages/plugins/finance/doc/index.mdpackages/plugins/finance/src/index.tspackages/plugins/finance/test/finance.test.tspackages/plugins/snap/README.mdpackages/tempo/.vitepress/theme/components/CatalogList.vuepackages/tempo/.vitepress/theme/data/catalog.jsonpackages/tempo/CHANGELOG.mdpackages/tempo/bin/build-catalog.mjspackages/tempo/doc/1-getting-started/installation.mdpackages/tempo/doc/1-getting-started/tempo.cookbook.mdpackages/tempo/doc/2-core-concepts/tempo.config.mdpackages/tempo/doc/2-core-concepts/tempo.format.mdpackages/tempo/doc/2-core-concepts/tempo.mutate.mdpackages/tempo/doc/2-core-concepts/tempo.parse.mdpackages/tempo/doc/3-extending-tempo/tempo.namespace.mdpackages/tempo/doc/3-extending-tempo/tempo.plugin.mdpackages/tempo/doc/8-project-and-support/commercial.mdpackages/tempo/doc/8-project-and-support/migration-guide.mdpackages/tempo/doc/8-project-and-support/releases/v3.x.mdpackages/tempo/package.jsonpackages/tempo/src/module/module.format.tspackages/tempo/src/support/support.init.tspackages/tempo/src/tempo.version.tspackages/tempo/test/discrete/format.test.ts
1 participant
Summary by CodeRabbit
New Features
shortandlongformatting modifiers for dates, weekdays, months, eras, and time zones.Documentation
Chores