Closed
Bug 2058922
Opened 2 months ago
Closed 2 months ago
test-manifest-toml linter should report issues as line 0, so that they show up in phabricator
Categories
(Developer Infrastructure :: Lint and Formatting, defect, P2)
Developer Infrastructure
Lint and Formatting
Tracking
(firefox155 fixed)
RESOLVED
FIXED
155 Branch
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(1 file)
Currently, the test-manifest-toml linter reports the section line number for an error or warning, because tomlkit doesn't report line information (probably this issue).
If I make a change part way down a toml file and that change causes an error or warning, then the issue is not displayed in phabricator because it is reported as line 1, which was not one of the modified lines.
According to the code-review-bot team, we can change the linter to report the line as null, which it will then see as affecting the whole file, and hence report it at the start of the file.
| Assignee | ||
Comment 1•2 months ago
|
||
Looking at the code a bit deeper - if a condition has failed, then we do calculate where the condition is, so I wonder if we can do something better for the section titles.
| Assignee | ||
Comment 2•2 months ago
|
||
Updated•2 months ago
|
Assignee: nobody → standard8
Status: NEW → ASSIGNED
Pushed by mbanner@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/8b39f0393b35
https://hg.mozilla.org/integration/autoland/rev/070c5d11dc91
Change the test manifest toml linter to report the sections that are out of order and the line number. r=linter-reviewers,sylvestre
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox155:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•