Closed Bug 1634122 Opened 5 years ago Closed 5 years ago

INI linter won't allow the same key name in different sections

Categories

(Developer Infrastructure :: Lint and Formatting, defect, P3)

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bytesized, Unassigned)

References

Details

STR:

  1. Create this file in the tree at this path: browser/locales/en-US/test.ini:
[Section1]
Key1=String1

[Section2]
Key1=String1
  1. Run ./mach lint browser/locales/en-US/test.ini

Expected Results:

Linter will emit no errors

Actual results:

c:/mozilla-central-secondary/browser/locales/en-US/test.ini
  2:1  error  Duplicate string with ID: Key1  (l10n)
  5:1  error  Duplicate string with ID: Key1  (l10n)

✖ 2 problems (2 errors, 0 warnings)
Blocks: 1621696

As the triage owner, do you think this bug might be fixed soon? I have a patch that needs to be merged soonish, and I'm trying to figure out whether I ought to wait for this to be fixed, or restructure my localization INI to avoid this bug.

Flags: needinfo?(ahal)

Redirecting to Axel. You should be able to add an exclusion to your file in tools/lint/l10n.yml as well.

Flags: needinfo?(ahal) → needinfo?(l10n)
Priority: -- → P3

The linter works as expected, our support for INI files in the l10n toolchain is at "whatever crashreporter needed at the time".

As the linter is right, resolving this as INVALID.

I'll add more detail in bug 1621700.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(l10n)
Resolution: --- → INVALID
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.