search

pact-foundation / roadmap

Developer Relations @ Pact - Your map to the Pact landscape for all-comers (maintainers, contributors, users, newbies)
https://pact.io/
MIT License
39 stars 6 forks source link

Support a communication method for announcing deprecations #48

Open canny[bot] opened 4 days ago

canny[bot] commented 4 days ago

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

canny[bot] commented 4 days ago

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

YOU54F commented 3 days ago

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 commented 3 days ago

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 commented 3 days ago

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