Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Enhance Exception Messages with shortID for JSON Elements #496

Open
Freezor opened this issue Jun 15, 2024 · 2 comments
Open

Enhance Exception Messages with shortID for JSON Elements #496

Freezor opened this issue Jun 15, 2024 · 2 comments

Comments

@Freezor
Copy link

Freezor commented Jun 15, 2024

Hi @mristin,

As I navigate through the project, I've noticed issues with exception messages in the AASX Server and package explorer. Currently, they indicate the node and line in JSON files where errors occur, but this can be challenging for large files and isn't very user-friendly. It would greatly improve usability if exception messages could also include the shortID of the failing JSON element.

Could you please share your thoughts on this idea? Do you know if this enhancement could be implemented quickly or where I should take a look to provide a PR for that feature?

Thank you!

@mristin
Copy link
Contributor

mristin commented Jun 16, 2024

Hi @Freezor ,
We implemented aas-core-codegen to be meta-model agnostig as meta-model changed fundamentally so many times. Most attributes and instances do not have a meaningful value-only path.

As far as I know, the value-only paths can not be generated automatically either. Your best bet is to manually map instances and attributes to value-only paths.

Btw., are you referring to serialization or to validation errors?

@Freezor
Copy link
Author

Freezor commented Jun 16, 2024

Hi. I might get back to you on that, but it is concerning the deserialization. Maybe there is another solution for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants