AnalyticalContext.DerivedDimension #367
Draft
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
| @@ -159,6 +159,9 @@ | |||
| <Property Name="Dimension" Type="Core.Tag" Nullable="false" DefaultValue="true"> | |||
| <Annotation Term="Core.Description" String="The property holds the key of a dimension" /> | |||
| </Property> | |||
| <Property Name="DerivedDimension" Type="Core.Tag" Nullable="false" DefaultValue="true"> | |||
| <Annotation Term="Core.Description" String="The value of the dimension is completely determined by the values of other dimensions" /> | |||
There was a problem hiding this comment.
Wouldn't it be useful to know what the other dimensions are?
There was a problem hiding this comment.
Are the "other dimensions" exactly the "ContextDefiningProperties"? Then we can specify that here.
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.
Only necessary if we want to distinguish between the postcode use case and the virtual element use case. We see no need for that at the moment.