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
People can merge new markdown files into rules that don't match any of the recognized content types. There have been several occasions where people have merged in a new rule and it hasn't gone live because it was placed in the wrong folder/had the wrong name.
💡Solution
We can add a validation check that uses the diff to check if any of the new content matches an existing category using the file path.
Tasks
Update rules validator to check the directory of new files to see if they fit an existing category
Update the validator to check the category of the new markdown file (If the path doesn't match) to generate an informative error message
Acceptance Criteria
All existing rules pass the new validation check (I have a script that can check this, message @Calinator444 if needed)
Important Information
Here's a list of recognized content types:
Category
File Path
Purpose
Rules
./rules/<rule-name>/rule.md
A markdown file containing the content for the article
CC: @bradystroud
The Pain 🤕
People can merge new markdown files into rules that don't match any of the recognized content types. There have been several occasions where people have merged in a new rule and it hasn't gone live because it was placed in the wrong folder/had the wrong name.
💡Solution
We can add a validation check that uses the diff to check if any of the new content matches an existing category using the file path.
Tasks
Acceptance Criteria
Important Information
Here's a list of recognized content types:
./rules/<rule-name>/rule.md
./categories/<top-category-name>/<category-name>.md
./categories/<top-category-name>/index.md
./categories/index.md
The text was updated successfully, but these errors were encountered: