feat: rename no-render-in-setup to no-render-in-lifecycle
#649
Conversation
This file contains 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
BREAKING CHANGE: rename no-render-in-setup to no-render-in-lifecycle
MichaelDeBoey
changed the title
no-render-in-setup to no-render-in-lifecycle
|
🎉 This PR is included in version 6.0.0-alpha.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
MichaelDeBoey
added
the
BREAKING CHANGE
MichaelDeBoey
pushed a commit
that referenced
this pull request
Oct 4, 2022
BREAKING CHANGE: `no-render-in-setup` is now called `no-render-in-lifecycle`
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.
BREAKING CHANGE: rename no-render-in-setup to no-render-in-lifecycle
Checks
npm run generate:rules-list)npm run generate:configs)Changes
no-render-in-setuptono-render-in-lifecycleso it's not confused with preventing renders nested in a setup function.Context
Resolves #625.