You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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?
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!
The text was updated successfully, but these errors were encountered: