Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide mechanism for renaming rules #955

Open
tripleee opened this issue Nov 14, 2022 · 4 comments
Open

Provide mechanism for renaming rules #955

tripleee opened this issue Nov 14, 2022 · 4 comments
Labels
area: data edits Issues which require someone (usually @Undo1) with higher access to fix records area: ui Anything to do with the user interface, particularly UX concerns type: feature request Requests for a new feature.

Comments

@tripleee
Copy link
Member

Some of the rules in Smoke Detector have misleading or otherwise unfortunate names. It would be nice if there was a way to change the description of a rule without losing previous tracking of its performance.

My off-the-cuff proposal would be to have a table of historic rule names mapping back to whatever a rule is currently called, so that we can update rule descriptions when there is a need.

A common complaint is the "URL fragment" rule description which is technically misleading; see also this discussion in SOCVR: https://chat.stackoverflow.com/transcript/message/55521065#55521065

@sri-shree
Copy link

sri-shree commented Nov 14, 2022

Its about nationality. Hindi != Nepali. Both use devanagari fonts, Please don't mess with us. Rename please.

@sri-shree
Copy link

Hindi +> Nepali +> (language) +> Devanagari Font

@makyen
Copy link
Contributor

makyen commented Nov 14, 2022

In order to fully change a reason name, it would be necessary to change the why text in every post which had been reported for that reason. That's definitely non-trivial and something that might needed to be coded separately for each change contemplated, particularly given historical changes to the format of the why text.

In addition, the change in name would need to either be perfectly coordinated in time between MS and SD, or there would need to be a concept of name aliases created, such that SD could report posts using either reason name and have it map to the same reason ID within MS.

@tripleee
Copy link
Member Author

Japanese vs Chinese has also been a recurring topic; see e.g. https://chat.stackexchange.com/transcript/message/63276307#63276307 and earlier in https://chat.stackoverflow.com/transcript/message/56087282#56087282

@makyen makyen added type: feature request Requests for a new feature. area: data edits Issues which require someone (usually @Undo1) with higher access to fix records area: ui Anything to do with the user interface, particularly UX concerns labels Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: data edits Issues which require someone (usually @Undo1) with higher access to fix records area: ui Anything to do with the user interface, particularly UX concerns type: feature request Requests for a new feature.
Development

No branches or pull requests

3 participants