TASK: Rename neos backend container #2848
Merged
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
markusguenther
force-pushed
the
task/rename-backend-container
branch
2 times, most recently
from
490308f
to
92b507e
Compare
Rename the container from neos-new-backend-container to neos-backend-container. The emberjs content module has been removed for 5.0 and now we rename the backend container as we have no old and new one anymore. The can cause issues when the third party code rely on the neos-new-backend-container id. Related: neos#2828
markusguenther
force-pushed
the
task/rename-backend-container
branch
from
92b507e
to
fe74b7e
Compare
4 tasks
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.
Rename the container from
neos-new-backend-containertoneos-backend-container. The emberjs content module has been removed for 5.0 and now we rename the backend container as we have no old and new one anymore.This can cause issues when the third party code rely on the neos-new-backend-container id.
Related: #2828
Fixes: #2849