Variation: Rethink the segment model#23060
Draft
kjac wants to merge 6 commits into
Draft
Conversation
…ch as it no longer plays a role in validation
nielslyngsoe
added
the
state/sprint-candidate
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Prerequisites
Description
The Management API (and related services for content editing introduced alongside it) has from day 1 hinted at segments being able to exist "on their own", for example by:
However, segments only ever exist as an "optional override" of the default (
null) segment. This applies both at document level and at property level.This PR removes segment notation of all models through the layers where they do not make sense.
Testing this PR
TBD
This item has been added to our backlog AB#69021