Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Better / verbose error reporting #314

Open
viraptor opened this issue Aug 1, 2024 · 0 comments
Open

Better / verbose error reporting #314

viraptor opened this issue Aug 1, 2024 · 0 comments

Comments

@viraptor
Copy link

viraptor commented Aug 1, 2024

Description

The errors produced by structurizr are very opaque. When something fails, it should tell more details.

For example:

The element "customer" can not be added to this type of view at line 10

Useful context that would save me lots of time in this case would be something like:

The element "customer" can not be added to view of type XXX at line 10
"customer" has type XXX, defined in XXX at line XXX.
DSL reference for allowed types in this context is at https://XXX

Please save me from manually searching the code and hunting down why "computer says NO".

Priority

I have no budget and there's no rush, please add this feature for free

More information

No response

@simonbrowndotje simonbrowndotje transferred this issue from structurizr/lite Aug 1, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant