Add basset:clear to upgrade guide #625
Merged
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
Member
|
Hello @jnoordsij Thanks for this PR I will ask @pxpm to check it and if everything is ok we will merge soon. Cheers. |
Contributor
|
Hey @jnoordsij hope you are doing well. Thanks for the PR 🙏 |
github-project-automation
bot
moved this from Needs Testing, Review or Docs
to Done
in This week
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When quickly checking out the v7 alpha for possible incompatibilities with my app (first look shows that it's running fine btw, keep up the good work!), I noticed that my local environment erred when trying to render views. Given that this originated from some basset call, I guessed that clearing bassets would solve the issue and it did. I think however that this warrants adding it as a recommended step to the migration guide.