chore: add docs about about new field #1062
Merged
Conversation
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
dks333
reviewed
Aug 29, 2025
Comment on lines
+595
to
+609
| ```json | ||
| { | ||
| "interaction": { | ||
| "drilldown": true // Force navigation to first page when a user expands a dropdown | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| ```json | ||
| { | ||
| "interaction": { | ||
| "drilldown": false // Never navigate, only expand/collapse | ||
| } | ||
| } | ||
| ``` |
There was a problem hiding this comment.
we should also add this property in /settings page
There was a problem hiding this comment.
Sounds good. I can move it there.
skeptrunedev
force-pushed
the
sk/add-docs-on-drilldown
branch
from
994ae86 to
8f2fe8d
Compare
dks333
approved these changes
Aug 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Documentation changes
Add new docs about the new
interaction.drilldownfield.For Reviewers
When reviewing documentation PRs, please consider:
✅ Technical accuracy
✅ Clarity and completeness
✅ User experience