Support a communication method for announcing deprecations

[canny]

https://pact.canny.io/admin/board/feature-requests/p/support-a-communication-method-for-announcing-deprecations

[canny]

This issue has been linked to a Canny post: Support a communication method for announcing deprecations 🎉

[YOU54F]

Tim Jones - February 23, 2021

Could you elaborate a bit on this? In JS, we emit warnings when deprecated features are used, but I feel like that's not what you're looking for.

[YOU54F]

Tim Jones - February 23, 2021

Could you elaborate a bit on this? In JS, we emit warnings when deprecated features are used, but I feel like that's not what you're looking for.

Matt Fellows - February 23, 2021

Tim Jones: We get this question in Pactflow a bit also. I can see an example where a provider marks a field as deprecated somehow (via the broker, presumably), and when the consumer runs it's local tests or can-i-deploy, feedback could be provided that a certain field is going to be removed.

[YOU54F]

Matt Fellows - February 23, 2021

Hey folks , i was socializing Pact with engineering teams. one question that came out is how do we inform Consumers early and technically of APIs that are planned to be depreciated in incoming releases and encourage them not to use it . This is one of the major questions coming out from the socialization sessions with engineering teams .

From this thread: https://pact-foundation.slack.com/archives/C9VPNUJR2/p1614000831010200