-
Notifications
You must be signed in to change notification settings - Fork 16
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
Better Error reporting #91
Labels
discussion
Things that need some thinking, and feedback from several to find consensus first.
Comments
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
discussion
Things that need some thinking, and feedback from several to find consensus first.
This ticket collects things to improve on error reporting, when the tools get incorrect input.
If no Interface is in the YAML, then no output. The D-Bus generator doesn't fail until the XML-reformatting where it says there is no start node (with an ugly exception backtrace).
Instead, check that an Interface node exists and/or check if generation result is empty, and report it to the user.
Related to the above, the current template-driven generators like BAMM, DTDL, and protobuf need to be updated for Interface. They don't fail because they just loop over "all methods in the Namespace", etc. So if there aren't any, the output will be mostly empty. Anyhow, perhaps this could be considered correct behavior for a file without an Interface node, but they should be updated.
Ultimately, add a check for Interface node, in the generic
ifexgen
- at least it probably should output a warning.The text was updated successfully, but these errors were encountered: