0.7.3 Release #291
Merged
0.7.3 Release #291
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
enable usage of async rerender_on on component-level
Update matestack-ui-core.js*
fixed form component usage on component-level
Adding ES5 transpiling
Issue 255
Revert "ES5 transpiling"
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.
Changelog
v0.7.3
Merged PRs
Solved Issues
Potential Breaking Change - Migration Note
Until
0.7.2.1, we included allActionViewmodules inMatestack::Ui::StaticComponentandMatestack::Ui::DynamicComponent. As we didn't use these modules in all of our core components, we decided to move theActionViewmodules to the newMatestack::Ui::StaticActionviewComponentandMatestack::Ui::DynamicActionviewComponentclass. If you useActionViewmodules in your components, you have to change the class you inherit from. This might be a potential breaking change for some users - we are not bumping to 0.8.0 as we don't break explicit specified behavior. If you have any problems, reach out via gitter!