[YAMLEXT-3] Improve logging and possibly avoid exceptions when syntax is incorrect Created: 28/Sep/16 Updated: 16/Mar/23 Resolved: 16/Mar/23 |
|
| Status: | Closed |
| Project: | Yaml extensions (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
In some cases where something is not configured correctly a log message could help the developer more quickly and painlessly achieve there goal. I'll try to identify a few of these cases. Ideally problems would be reported as soon as the YAML file is detected and loaded by the system, not only when the definition is used. If possible, log messages should specify the file where the problem occurs. When using !extend, if the target file does not exist, an exception occurs. It would be helpful if a simple log message would be printed first. And possibly the exception could be avoided. When there is a space between the tag and the address (!extend: /mtk/dialogs/components/link.yaml), a note should be written to log. Currently one gets a seemingly unrelated exception. |
| Comments |
| Comment by Daniel Kasmeroglu [ 20/Dec/17 ] |
| Comment by Adam Jones [ 16/Mar/23 ] |
|
Closing due to project being archived. |