Skip to content

Conversation

@krzyzak
Copy link

@krzyzak krzyzak commented Jan 31, 2025

Adds support for custom translation exceptions via configuration. Users can now specify additional strings that should be exempt from translation requirements, alongside the default NO_TRANSLATION_NEEDED list. This is useful for:

  • Brand names
  • Custom HTML entities
  • Project-specific terms
  • Any strings that shouldn't trigger translation warnings

Usage example:

linters:
  HardCodedString:
    ignored_words:
      - MyBrand
      - "§"

@krzyzak
Copy link
Author

krzyzak commented Jan 31, 2025

I have signed the CLA!

@krzyzak krzyzak force-pushed the add-ignored-words-to-hardcoded-string-linter branch from ee29308 to 32985b4 Compare January 31, 2025 14:38
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.

1 participant