feat(quantic): addition of the ability to generate automatic ranges in timeframe facets - #8218
feat(quantic): addition of the ability to generate automatic ranges in timeframe facets#8218mmitiche wants to merge 3 commits into
Conversation
🦋 Changeset detectedLatest commit: 67d612a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
@coveo/atomic
@coveo/atomic-hosted-page
@coveo/atomic-legacy
@coveo/atomic-react
@coveo/auth
@coveo/bueno
@coveo/create-atomic
@coveo/create-atomic-component
@coveo/create-atomic-component-project
@coveo/create-atomic-result-component
@coveo/create-atomic-rollup-plugin
@coveo/create-ui
@coveo/headless
@coveo/headless-react
@coveo/relay
@coveo/shopify
commit: |
There was a problem hiding this comment.
Pull request overview
This PR adds support in QuanticTimeframeFacet for Headless-driven automatic date ranges by exposing a new public generateAutomaticRanges boolean API (defaulting to false to preserve current behavior) and forwarding it to the underlying buildDateFacet options. It also updates the Quantic examples community component and adds unit test coverage.
Changes:
- Added
@api generateAutomaticRanges(defaultfalse) toQuanticTimeframeFacetand forwarded it intobuildDateFacetoptions. - Added a unit test to verify the controller is built with
generateAutomaticRanges: truewhen configured. - Updated the example community component to surface the new option, and added a changeset for
@coveo/quantic.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| packages/quantic/force-app/main/default/lwc/quanticTimeframeFacet/quanticTimeframeFacet.js | Exposes generateAutomaticRanges and forwards it to the Headless date facet controller. |
| packages/quantic/force-app/main/default/lwc/quanticTimeframeFacet/tests/quanticTimeframeFacet.test.js | Adds unit coverage for the new generateAutomaticRanges initialization behavior. |
| packages/quantic/force-app/examples/main/lwc/exampleQuanticTimeframeFacet/exampleQuanticTimeframeFacet.js | Adds a configurator option so the feature can be toggled in the examples community. |
| packages/quantic/force-app/examples/main/lwc/exampleQuanticTimeframeFacet/exampleQuanticTimeframeFacet.html | Wires generate-automatic-ranges into the example facet markup. |
| .changeset/quantic-timeframe-facet-automatic-ranges.md | Declares a minor version bump for the new public API. |
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
SFINT-6091
The problem
Previously
QuanticTimeframeFacethardcodedgenerateAutomaticRanges: falseon the underlyingDateFacetcontroller, so the component could only show ranges manually declared via c-quantic-timeframe children.The solution
This PR Exposes
generateAutomaticRangesas a public property (default false, preserving current behaviour) and forwards it into buildDateFacet's options since range generation itself is already handled by headless.Additionally wired this new property to the example component present in the community so the option is explorable/testable there.