
- files should be prefixed with code_ocean/ - the markdown editor is part of the application (helper)
1.5 KiB
1.5 KiB
PyLint translation
The files in this folder are used to translate PyLint results from the original English output to German.
Structure
The following hierarchy has been implemented:
severity
of the linter check result- The
severity_name
translates the severity itself
- The
- code of the linter check result
- A list of required values for the actual translation
example
: not used anywhere, just for reference when editing this yml filename
: Title of the linter checkregex
: A regex used to translate dynamic parts with named capture groupsreplacement
: A fix replacement translation which is used instead of the original English output. It may refer to one of the named capture groups to include dynamic content from the English originallog_missing
: Specifies whether missing translations should be logged to Sentry
- Optionally a named capture group from the regex
- A list of fix translations for values / matches of the named capture group
Additional information for error.syntax-error
replacement
:context
, andline
are matched as well but are currently not usedwhat.invalid decimal literal
: An example would be100_years
waht_exactly
:- It must start with a space character
- The following errors are used in the context of an f-string:
empty expression not allowed
single
unmatched
- The following capture groups are used without translation:
actual
suggestion
context
line