FEATURE: WorkspaceName with reference for unused contentStream #5167
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.
As written in #5034 (comment) we actually decided against it, but look how pretty it seems? :D
introduces the syntax
WorkspaceName('cs:<ContentStreamId>')
... that way we'd now what to write inside the fetched workspace name of a "forbidden" node.But we initially didnt want to go down this road:
Neos 9.0 weekly - 01-03-2024
Additionally we should restrict the workspace name to be stricter: #5125 and discuss if
fromString
should allow thecs:
notation.TODO
1.) discuss if we are okay with being able to reference the content stream id in a node address per uri:
2.) disallow the 'fake' workspace name to be used in commands like createWorkspace, or modify a node.
3.) check other usages where a fake workspace name can be passed and see if we should allow it there.