-
Notifications
You must be signed in to change notification settings - Fork 195
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
Standardize user mention formatting #289
Comments
I'm assuming |
I wouldn't doubt that it's still used. However, it can be a bit misleading and confusing if you haven't inspected the source code, that's all I'm saying. I'm seeking standardization. Furthermore, we shouldn't be afraid of removing deprecations. It's not really a "breaking change" either. The most you'll get are a few logs where the user is mentioned. Dragory can post an announcement as well, if required. |
Currently the main blocker for removing deprecations is the lack of a robust way to programmatically edit and migrate server configs (to remove/rename/etc. the deprecated options from them). There are some solutions I'm looking into; the main obstacle is preserving YAML formatting and comments. The yawn-yaml package looks very promising in that area. |
Yeah, that's usually a problem with removing deprecations. Maybe you could officially announce it as deprecated along with plans to remove it with a couple months and suggest the alternative solution? |
According to LogsPlugin.ts#L123,
ping_user
is deprecated, implying thatallow_user_mentions
is the preferred option. Yet in getLogMessage.ts#L92, the user mention formatting result used in logs is determined by bothping_user
andallow_user_mentions
.If
ping_user
was internally marked as deprecated, why is it still being used to determine a user mention formatting result?Instead, could we just standardize
allow_user_mentions
as the determining condition for whether or notverboseUserMention()
is called instead ofverboseUserName()
?The text was updated successfully, but these errors were encountered: