-
-
Notifications
You must be signed in to change notification settings - Fork 138
Centralize community rules #944
Copy link
Copy link
Closed
Labels
area: APIRelated to or causes API changesRelated to or causes API changesarea: frontendRelated to site content and user interactionRelated to site content and user interactionpriority: 3 - lowLow PriorityLow Prioritytype: enhancementChanges or improvements to existing featuresChanges or improvements to existing features
Metadata
Metadata
Assignees
Labels
area: APIRelated to or causes API changesRelated to or causes API changesarea: frontendRelated to site content and user interactionRelated to site content and user interactionpriority: 3 - lowLow PriorityLow Prioritytype: enhancementChanges or improvements to existing featuresChanges or improvements to existing features
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently, the same rules are persisted in 2 different places
pydis_site/apps/api/views.pyandpydis_site/apps/content/resources/rules.mdOver the past month or so, we've had two rule updates in one of the files only, leaving the other forgotten.
It would be nice to put the rules in one place only in order to avoid missing out on one over the other.
Note
I'm not even sure this is something we'd want to do, so just putting it out there (@jchristgit you're the site master, so you might have better scope knowledge here)
An idea off the top of my head is:
Since one is put in an
.mdfile, we can't really achieve intepolation of the content of that file.So maybe the view can parse the file & extract the rules based on their numbers and maps them to a tuple along with the keywords.