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.
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
Font Size Picker: Allow non-integers as simple CSS values and in hints #36636
Font Size Picker: Allow non-integers as simple CSS values and in hints #36636
Changes from all commits
347ea3a
3f39aa9
0d6544f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Looking at the changes made in #36420, I believe that we should also apply the change on the JSDoc for the
size
param (i.e. changing its type to be onlystring
)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.
The changes here were slightly different to #36420. It honours what was documented in terms of the param accepting
string|number
. The tests also cover both strings and numbers.The
FontSizePicker
docs themselves also include numericalsize
values. Should we not maintain compatibility with that?In light of that, do you still believe I should restrict this?
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.
You actually made a few good points — let's leave it as-is (and thank you for looking into it)
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 was wondering why you changed from
split
tomatch
. I was expecting a change in the regex.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.
Honestly, this wasn't a conscious choice. It came from when I copied the original change.
On a closer look though,
match
appears a little cleaner in terms of its results. I don't feel strongly about it, so if there is a good reason to change it back tosplit
I can.