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

[V3 common filters/context/modlog] Update for spoilers #2401

Merged
merged 9 commits into from
Feb 16, 2019
Merged

[V3 common filters/context/modlog] Update for spoilers #2401

merged 9 commits into from
Feb 16, 2019

Conversation

mikeshardmind
Copy link
Contributor

@mikeshardmind mikeshardmind commented Feb 1, 2019

Spoilers are not handled in usernames and other untrustable user content.

This also wraps some fields of the modlog with the same sanitization.

Type

  • Bugfix
  • Enhancement
  • New feature

Description of the changes

No longer done as a breaking change per discussion in discord.

Michael Hall added 2 commits January 31, 2019 22:56
Spoilers are not handled in usernames and other untrustable user
content.

This is technically a breaking change if anyone is already having their bot send spoilered content, but includes
documentation on getting the previous behavior instead.
@Tobotimus Tobotimus added Type: Enhancement Something meant to enhance existing Red features. QA: Needed and removed QA: Unassigned labels Feb 3, 2019
@Tobotimus Tobotimus self-assigned this Feb 16, 2019
@Tobotimus Tobotimus self-requested a review February 16, 2019 00:13
@Tobotimus Tobotimus added QA: Passed Used by few QA members. Has been approved by the assigned QA member(s). and removed QA: Needed labels Feb 16, 2019
@Tobotimus Tobotimus merged commit d13bf37 into Cog-Creators:V3/develop Feb 16, 2019
Tobotimus pushed a commit that referenced this pull request Feb 16, 2019
This also wraps some fields of the modlog with the same sanitization, as well as the `[p]names` command.
@mikeshardmind mikeshardmind deleted the spoiler-handling branch December 26, 2019 17:06
@Jackenmen Jackenmen added this to the 3.0.1 milestone Nov 17, 2020
@Jackenmen Jackenmen added the Type: Bug Unexpected behavior, result, or exception. In case of PRs, it is a fix for the foregoing. label Jul 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA: Passed Used by few QA members. Has been approved by the assigned QA member(s). Type: Bug Unexpected behavior, result, or exception. In case of PRs, it is a fix for the foregoing. Type: Enhancement Something meant to enhance existing Red features.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants