We've been using automat-client in DCR. Over time it appears there's been a drift between the 'canonical' types here (in support-dotcom-components) and the types there (in automat-client) - for example the Targeting type in Metadata (used for the ReaderRevenueEpic in DCR) doesn't include the required hasOptedOutOfArticleCount property, which means we have had to add a workaround in DCR where automat-client is consumed.
We felt that, rather than maintaining the types in two places, the types here in support-dotcom-components should be shared via a mechanism like an NPM package, and ingested by the other repositories.
Does this sound sensible?
We've been using
automat-clientin DCR. Over time it appears there's been a drift between the 'canonical' types here (insupport-dotcom-components) and the types there (inautomat-client) - for example theTargetingtype inMetadata(used for the ReaderRevenueEpic in DCR) doesn't include the requiredhasOptedOutOfArticleCountproperty, which means we have had to add a workaround in DCR whereautomat-clientis consumed.We felt that, rather than maintaining the types in two places, the types here in
support-dotcom-componentsshould be shared via a mechanism like an NPM package, and ingested by the other repositories.Does this sound sensible?