New output format in 0.6.0 stopped distinguishing warnings from errors
Bug #1782960 reported by
Ben Stoutenburgh
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bash8 |
New
|
Undecided
|
Unassigned |
Bug Description
All warnings now show as E in the output.
```
ben@warden816:
bashate/
bashate/
bashate/
bashate/
4 bashate warning(s) found
```
At a tired glance, looks like logic for picking W or E is assigned to the 'warn' key but not used in the print statement in log_error().
To post a comment you must log in.
For clarifcation, prior to 0.6.0 warnings (whether from the message's default, or through the --warn option) would show up with a [W]. Looks like intention was to change error codes to be Wxxx or Exxx going forward.
``` ~/repos/ bashate (master u=)$ bashate bashate/ tests/samples/ E042_bad. sh tests/samples/ E042_bad. sh : L2 tests/samples/ E042_bad. sh : L6 tests/samples/ E042_bad. sh : L10 tests/samples/ E042_bad. sh : L11
ben@warden816:
[W] E042: local declaration hides errors: ' local foo=$(ls)'
- bashate/
[W] E042: local declaration hides errors: ' local foo=`ls`'
- bashate/
[W] E042: local declaration hides errors: ' local foo="$(ls)"'
- bashate/
[W] E042: local declaration hides errors: ' local bar="`ls`"'
- bashate/
4 bashate warning(s) found
```