Update lightningcss #4070
Merged
Update lightningcss #4070
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
|
Build successful! 🎉 |
ktabors
previously approved these changes
Feb 15, 2023
Thanks for the reminder, Chromatic shows bad. We have some new specificity collisions |
This reverts commit ff0f269.
|
Build successful! 🎉 |
devongovett
approved these changes
Feb 16, 2023
|
Build successful! 🎉 |
LFDanLu
approved these changes
Feb 16, 2023
|
Build successful! 🎉 |
|
## API Changes
unknown top level export { type: 'identifier', name: 'Column' } |
|
ran docs differ, seems good to me |
devongovett
pushed a commit
to adobesamr/react-spectrum
that referenced
this pull request
Feb 22, 2023
update lightnincss
dannify
added a commit
that referenced
this pull request
Feb 23, 2023
* Adding parseDuration functionality Adds parseDuration function to internationalized/date package to parse ISO 8601 Duration strings into a DateTimeDuration object * separating parseDuration documentation to separate PR * corrects formatting issues * corrects documentation for parseDuration function * fix deps in @react-types/list (#4073) * fix(#4067): Storybook Provider addon: Express input:checkbox requires id to be labelled by htmlFor prop (#4068) * Explain Proxy in TableView (#4072) Explain proxy usage in TableView * Update lightningcss (#4070) update lightnincss * fix(#4078): MobileComboBox: searchbox should not have aria-expanded property (#4079) * Get rid of dupe id in DatePicker/useDatePicker (#4085) * Getting rid of duplicated id present in presentational element * generate a separate id instead to avoid useField complaining in useDateField a date field in a datepicker/rangepicker gets the field props removed from it, but we still need to call useField in useDateField which will complain that there isnt a aria labelledby so we still need to pass the field props * Code changes from docs-ts branch (#4090) * Add docs to more pages, and small wording updates --------- Co-authored-by: Daniel Lu <dl1644@gmail.com> Co-authored-by: Danni <drobinson@livefyre.com> Co-authored-by: Reid Barber <reid@reidbarber.com> Co-authored-by: Michael Jordan <mijordan@adobe.com> Co-authored-by: Robert Snow <rsnow@adobe.com> Co-authored-by: Devon Govett <devongovett@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #3991
Figured it was a good opportunity to update parcel as well. However, if we want to restrict it, I can do that as well.
✅ Pull Request Checklist:
📝 Test Instructions:
🧢 Your Project: