-
Notifications
You must be signed in to change notification settings - Fork 149
Add no-render-in-setup
rationale to docs
#696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
documentation
Improvements or additions to documentation
good first issue
Good for newcomers
released on @alpha
released
Comments
I assume you meant |
Oh gosh, yup. Just saw that mixup. |
no-node-access
rationale to docsno-render-in-setup
rationale to docs
Edited the issue and title, thanks for that. |
1 task
🎉 This issue has been resolved in version 6.0.0-alpha.14 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 5.10.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
documentation
Improvements or additions to documentation
good first issue
Good for newcomers
released on @alpha
released
Plugin version
5.9.1
What problem do you want to solve?
The rationale for
no-render-in-setup
is missing from the documentation.Your take on the correct solution?
Let's add the rationale to the documentation. This rationale was referenced in the feature request conversation here.
The rationale itself is here.
Anything else?
No response
Do you want to submit a pull request to implement this change?
Yes
The text was updated successfully, but these errors were encountered: