You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting the status of a component to deprecated, mdatagen should validate the presence of two additional fields in metadata.yaml:
One field that contains the date of the deprecation, in format YYYY-MM-DD ("2006-01-02" date parsing format)
One field that contains a non empty string with migration instructions. This is a free form field. It is reasonable for someone to enter "No migration is offered for this component", and reviewers of the change can discuss.
Those fields should surface in the README.md generated text.
The text was updated successfully, but these errors were encountered:
Component(s)
No response
Describe the issue you're reporting
When setting the status of a component to deprecated, mdatagen should validate the presence of two additional fields in metadata.yaml:
YYYY-MM-DD
("2006-01-02" date parsing format)Those fields should surface in the README.md generated text.
The text was updated successfully, but these errors were encountered: