Properly propagate config for metric when created from measure #12135
+19
−3
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.
Problem
Currently, metrics can be created by measures from proxy through the
create_metric:trueflag. It was flagged that theconfig.metawas not being propagated correctly to that metric even though whenconfig.metais listed in the semantic model all downstream elements gets that and in this case if the metric is a proxy to the measure, we should also get that value.Solution
Update the parser to pass the
config.metafield during when handlingcreate_metric=TrueChecklist