Stream: cds hooks
Topic: Make deprecation obvious?
Lloyd McKenzie (Mar 07 2019 at 17:28):
Should we do something in the menu to distinguish 'deprecated' hooks? E.g. mark them with strikethrough or something?
Lloyd McKenzie (Mar 07 2019 at 18:52):
I might also make the template italics so it's obviously distinct from the true hooks
Kevin Shekleton (Mar 08 2019 at 13:59):
Can we just remove them and archive them off on a wiki or something? I don't want a bunch of deprecated/unused hooks cluttering up that list
Lloyd McKenzie (Mar 08 2019 at 15:42):
You could have an italicized link to "deprecated hooks" if you wanted and then have a page that pointed to them. How quickly you can just "yank" them should probably be driven by your deprecation policy (which might want to be informed by the highest maturity level something's hit. Pretty reasonable to make something 0 or 1 just disappear. Might want to give some time for something 4 or 5 and for something normative, you'll probably want to adhere to FHIR's deprecation policy of a couple of balloted releases.
Josh Mandel (Mar 08 2019 at 18:55):
In general when we decide to deprecate something there should be a time window. That window could be immediate or extensive -- but I don't think deprecated hooks should disappear until that time when they were lapses. Links to them should not break during the transition window. but the content should be clearly marked and once the time window elapses the deprecated hooks should be removed from the main list.
Josh Mandel (Mar 08 2019 at 18:55):
For our recent deprecation decisions, we did not mark a time window, and I think "effective immediately" is just fine.
Lloyd McKenzie (Mar 08 2019 at 20:26):
I think hooks that may have hit production should remain discoverable and accessible.
Last updated: Apr 12 2022 at 19:14 UTC
