Closed tunetheweb closed 6 months ago
Alternatively we could introduce a new MetricWithAttributionType
with that definition (which would be consistent with MetricType
) and leave MetricWithAttribution
alone for now. Then make the MetricWithAttribution
change in v4, to avoid a breaking change for now incase we have any more v3 releases.
It does seem odd to have both interfaces and types defined though but maybe that's OK in this case?
@mcanu any thoughts here?
Anyone any more thoughts on this?
@brendankenny @mcanu @philipwalton
@brendankenny can you take a look at this and make a recommendation? I think any change here might be a breaking change, so it'd be good to get this in the v4 release if possible.
Also, once we have a decision we can update this PR's base branch to the v4 branch.
If there's going to be a breaking change, definitely switching to the unions at the top level would be ideal (e.g. get rid of Metric
and have MetricType
be the real thing, similar with MetricWithAttribution
), then move the types used for documentation to just be documentation.
I would love to give all the types a little refresh but I don't know if I'll have the time in the next ~24 hours if that's the goal for v4.
CLosing in favour of #471
Fixes #408