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
i want to be able to take untrusted user input which may contain legacy section symbol color codes and sanitize and tags from them before converting the section symbols to tags (because vise versa would cause the converted tags to be escaped)
The text was updated successfully, but these errors were encountered:
mmmmh, not sure why MiniMessage would care about any other format, especially unsupported legacy ones. there is no code in MiniMessage to convert legacy stuff either.
if you manually call the legacy serializer to convert legacy stuff, sanitizing that is on you, no?
basically, i don't understand the usecase, can you provide more context?
mmmmh, not sure why MiniMessage would care about any other format, especially unsupported legacy ones. there is no code in MiniMessage to convert legacy stuff either.
if you manually call the legacy serializer to convert legacy stuff, sanitizing that is on you, no?
basically, i don't understand the usecase, can you provide more context?
Take for example chat in Essentials. It has a format in the form of a translation string and multiple arguments that are passed to it: display name, prefix, chat message, etc. Because it has user supplied input, we have to sanitize it for tags but the chat message, display name, and prefix all may have section symbols in them. I understand they're not supported in the parser which is why I already wrote code to convert section symbols to minimessage but I obviously can't do that before I escape tags since that would lead to the converted message being escaped by eacapeTags
i want to be able to take untrusted user input which may contain legacy section symbol color codes and sanitize and tags from them before converting the section symbols to tags (because vise versa would cause the converted tags to be escaped)
The text was updated successfully, but these errors were encountered: