Report all parse errors in one pass
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/459)
In GitLab by [[Gitlab user @tristanvb]](https://gitlab.com/tristanvb) on Jul 6, 2018, 12:27
## Summary
[//]: # (Summarize the bug encountered concisely)
It would be desirable if at load time, BuildStream would not abort the load process immediately when an error is encountered, but instead continue to collect as many errors with the yaml as rationally possible, and report all the errors at once.
## Other relevant information
[//]: # (Add the BuildStream version. Substitute below the "x" by "1", "2" or the right version. Add more than one version if necessary)
* BuildStream version affected: /milestone %BuildStream_v1.x
----
Contributor guide
Research direction
Start with the load-time YAML parsing behavior described in this issue and compare it with the original GitLab issue for context. Determine which parse errors can be collected in one pass without aborting, and consider the work complete when all rationally discoverable errors are reported together.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100