Repository navigation
fix: restrict FilterChip number column to numeric input #912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
bddfdad
fix: restrict FilterChip number column to numeric input
Shreyag02 e2d05d0
Merge branch 'main' into fix/filter-chip-number-input
Shreyag02 ce6cba3
fix: [filter-chip] keep trailing-decimal input as string, drop inputMode
Shreyag02 53e877f
test: [filter-chip] trim redundant tests, tighten docs and comments
Shreyag02 bedfc1b
fix: [filter-chip] send trailing-decimal input as a number
Shreyag02 d3e5a5d
fix: [filter-chip] start number chip empty for a non-numeric value
Shreyag02 1351341
fix: [filter-chip] show exponent values in full, reject Infinity
Shreyag02 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use Base UI NumberField primitive instead of all this custom logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the suggestion, Rohan. I did evaluate NumberField initially, but encountered a few issues when using it within the chip:
data-slot: Its input uses a differentdata-slot, so the chip's existing reset styles do not apply to it.field-sizing).Input.I agree the primitive would be a cleaner long-term option. Would you be okay with me addressing it in a follow-up PR, so this one stays limited to the validation fix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am talking about the BaseUI primitive NumberField, not our Apsara wrapped component
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Won't switch. I tried the Base UI
NumberFieldprimitive directly (Root + Input only) and hit these problems:12ableaves12abin the field and sends12, becauseparseNumberignores the letters.1,5is15in en-US, and1.5is15in de-DE.1000becomes1,000, and1.23456shows as1.235while the value stays1.23456.field-sizingisfixedand the width stays at 149px. It also doesn't match the chip's CSS, because the chip's reset rules target[data-slot="input"].-and.send nothing, so the table keeps the previous value.Pinning
localeandformatfixes some of this, but paste and layout would still need custom code. The code change would come out about the same size.