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

Allow the term "Mastercard" #9893

Merged
merged 1 commit into from Jun 29, 2021
Merged

Allow the term "Mastercard" #9893

merged 1 commit into from Jun 29, 2021

Conversation

coorasse
Copy link
Contributor

The new cop marks the term "Mastercard" as offensive.

Although they should rename the company to Maincard, that's not going to happen soon.

This PR allows the term Mastercard by default.

The new cop marks the term "Mastercard" as offensive.

Although they should rename the company to Maincard, that's not going to happen soon.

This PR allows the term Mastercard by default.
@duarme
Copy link

duarme commented Jun 29, 2021

image

😱

@schmijos
Copy link
Contributor

2021-06-29 at 09 18

@bbatsov
Copy link
Collaborator

bbatsov commented Jun 29, 2021

Hmm, this seems like a bug in the cop as I don't think that it should target master as part of a word. And yeah - the cop's a bit controversial, so we may end up disabling it by default, based on the feedback we receive from our users.

@bbatsov
Copy link
Collaborator

bbatsov commented Jun 29, 2021

//cc @tjwp - is looking for the problematic terms as part of another word a feature or bug from your perspective? To me it seems like a bug.

@ShockwaveNN
Copy link
Contributor

And yeah - the cop's a bit controversial, so we may end up disabling it by default, based on the feedback we receive from our users.

You got mine :)

#9895

@tjwp
Copy link
Contributor

tjwp commented Jun 29, 2021

//cc @tjwp - is looking for the problematic terms as part of another word a feature or bug from your perspective? To me it seems like a bug.

For my part this was intentional behavior and there was a test included to document that matching part of a word is expected: https://github.com/rubocop/rubocop/blob/master/spec/rubocop/cop/naming/inclusive_language_spec.rb#L24-L30

I think it makes sense to add an exclusion for Mastercard.

I'd also be onboard with disabling this cop by default and letting users provide the configuration that works for them.

@bbatsov
Copy link
Collaborator

bbatsov commented Jun 29, 2021

@tjwp Got it. Might be a good idea to add some option like ExactMatch or something along those lines.

@bbatsov bbatsov merged commit ba3e33e into rubocop:master Jun 29, 2021
koic added a commit to koic/rubocop that referenced this pull request Jun 29, 2021
… `FlaggedTerms` for `Naming/InclusiveLanguage`

Fixes rubocop#9895 and follow up rubocop#9893 (comment).

This PR sets `CheckStrings: false` and removes `master` from `FlaggedTerms` for `Naming/InclusiveLanguage`
because it has an unexpectedly impact for many users who give feedback.
bbatsov pushed a commit that referenced this pull request Jun 29, 2021
…edTerms` for `Naming/InclusiveLanguage`

Fixes #9895 and follow up #9893 (comment).

This PR sets `CheckStrings: false` and removes `master` from `FlaggedTerms` for `Naming/InclusiveLanguage`
because it has an unexpectedly impact for many users who give feedback.
@bbatsov
Copy link
Collaborator

bbatsov commented Jun 30, 2021

We've cut a new release with a more permissive configuration for the cop. It shouldn't be noisy for anyone at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants