Many legacy eslint warnings swamp actual errors
Bug #1554824 reported by
Richard Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
In Progress
|
Low
|
Matthew D. Wood |
Bug Description
Horizon's eslint output currently has many hundreds of warnings which drown out any linting output for new code.
Changed in horizon: | |
assignee: | nobody → Richard Jones (r1chardj0n3s) |
status: | New → In Progress |
Changed in horizon: | |
assignee: | Richard Jones (r1chardj0n3s) → Matt Borland (palecrow) |
Changed in horizon: | |
importance: | Undecided → Low |
milestone: | none → newton-1 |
Changed in horizon: | |
milestone: | newton-1 → newton-2 |
Changed in horizon: | |
milestone: | newton-2 → newton-3 |
Changed in horizon: | |
assignee: | Matt Borland (palecrow) → Matthew D. Wood (woodm1979) |
Changed in horizon: | |
milestone: | newton-3 → next |
To post a comment you must log in.
A *lot* of the warnings are about jsdoc errors, but we need to have a conversation about documenting our Javascript before those should be addressed. Also, the governance for this specifically says we should be using Sphinx. So there.
http:// governance. openstack. org/reference/ cti/javascript- cti.html