Potential error in docs or wrong versioning (v1.2.2) #350
-
|
Hello, guys! I'd like to discuss a potential issue with the new version of materialize (regarding either the documentation or the adopted version, itself). There are at least three undocumented changes that are present in v1.2.2:
My question is: Are those changes already in production? I'm asking it because those would be either breaking changes (except by the dark mode support), which would either require the package version to be updated to v2.x or mean that the docs which is currently available does not correspond to the latest release. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Hello @mauromascarenhas The new v2 will be much different in development terms (typescript and no jquery anymore) We should change the docs however to point that jQuery is not needed anymore. You can still use jQuery it in your projects. |
Beta Was this translation helpful? Give feedback.
-
|
Correct. There are currently no breaking changes in v1.2.2. Only the current development branches for v2 contain breaking changes. See also the link to the actual changes / commits: 1.2.1...1.2.2 The documentation / website uses a different version (v2 dev). See the v2 branch changes from v1.2.2 at 1.2.2...v2-dev https://github.com/materializecss/materialize/commits/gh-pages |
Beta Was this translation helpful? Give feedback.
-
|
Currently the the docs differ only in the data-property of autocomplete and chips. |
Beta Was this translation helpful? Give feedback.
-
|
Is there the possibility of replacing/rolling back the documentation content for v1.2.x so as to match the lastest release notes (at least for autocomplete)? |
Beta Was this translation helpful? Give feedback.
Hello @mauromascarenhas
yes that is correct! This is because we have no versioning system for the Docs in place yet.
@DanielRuf pointed out a possible solution. I will check that and hope we can implement this soon.
The new v2 will be much different in development terms (typescript and no jquery anymore)
but for the user there should be no much structural difference.
We should change the docs however to point that jQuery is not needed anymore. You can still use jQuery it in your projects.
So we need a docs-versioning system anyway to support different versions.