Release 2.2.2 #615
Merged
Release 2.2.2 #615
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
…prefixing and sourcemapping into one function
…ell to initial, implemented additional is-daterange-start + is-daterange-end classes and refactored styling to use pseudo selectors on newly created classes #360
…ng text field if present #558
… display font size adjustment when rendering multiple dates
…styling as todos in scss file
…; configured confirmation buttons to render when auto submit is false #558
remove overflow from cards
This fixes also the select issue with the label placement. The impact is not tested, but in that case we should offer a relocate function to move the dropdown manually.
Fix dropdown in modal
if we use class names instead of tag elements we should be at least consistent
fix(mixins): border none is missing from new button mixin
fix(_navbar): use .nav instead of nav
includes nested .inline class for .input-fields class elements
fix(_input-fields): display inline inputs fields actually inline
fix(_range): display bar for range in chrome browser
There was a problem hiding this comment.
Copilot reviewed 57 out of 73 changed files in this pull request and generated 1 comment.
Files not reviewed (16)
- package.json: Language not supported
- sass/components/_badges.scss: Language not supported
- sass/components/_breadcrumb.scss: Language not supported
- sass/components/_buttons.scss: Language not supported
- sass/components/_cards.scss: Language not supported
- sass/components/_carousel.scss: Language not supported
- sass/components/_chips.scss: Language not supported
- sass/components/_collapsible.scss: Language not supported
- sass/components/_collection.scss: Language not supported
- sass/components/_color-classes.scss: Language not supported
- sass/components/_color-variables.scss: Language not supported
- sass/components/_datepicker.scss: Language not supported
- sass/components/_dropdown.scss: Language not supported
- sass/components/_global.scss: Language not supported
- sass/components/_grid.scss: Language not supported
- sass/components/_materialbox.scss: Language not supported
Comments suppressed due to low confidence (2)
rollup.config.ts:114
- [nitpick] There is an inconsistency between the two SCSS processor implementations (one synchronous and one asynchronous). Unifying the approach can help prevent build-time inconsistencies.
postcss([autoprefixer]).process(css, { from: 'materialize.min.css' })
rollup.config.ts:156
- Removing the substring(1) workaround might reintroduce formatting issues that the original approach was addressing; please verify that the change does not cause regression.
transform: (contents) => [bannerText, contents.toString()].join('\n') // bug => workaround
Comment on lines
+113
to
+116
| processor: (css, map) => ({ | ||
| css: postcss([autoprefixer]).process(css, { from: 'materialize.min.css' }).toString(), | ||
| map | ||
| }) |
There was a problem hiding this comment.
postcss().process returns a Promise, so calling toString() immediately may result in an unexpected value. Consider using a synchronous API like processSync or handling the Promise appropriately.
Suggested change
| processor: (css, map) => ({ | |
| css: postcss([autoprefixer]).process(css, { from: 'materialize.min.css' }).toString(), | |
| map | |
| }) | |
| processor: async (css, map) => { | |
| const result = await postcss([autoprefixer]).process(css, { from: 'materialize.min.css' }); | |
| return { | |
| css: result.css, | |
| map | |
| }; | |
| } |
Copilot uses AI. Check for mistakes.
|
Hi @wuda-io ! Thank you for the hard job ! And also kudo to all contributors. Do you know when release 2.2.2 will be online on https://materializeweb.com ? |
|
@AurelienTisserand The release is now online. Also we can now mange the documentation versions better. Probably we should do some sort of upgrade manuals now from version to version to prevent issues. |
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.
Proposed changes
New Release! Please be patient and bring Materialize forward to get better and better.
Every help, support and funding is greatly appreciated!
A huge thanks to the developers who bring this project forward and test it continously in their projects.
Big Thanks to our sponsors and backers!
I hope we make this an awesome project and have a great community!
Thanks! ❤️
Types of changes
Checklist: