-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
sdformat: Should ensure filename / lineno is included in diagnostic mechanism #17053
Comments
FYI in Drake's URDF parser, we have a sugar class to assist with reporting line numbers: detail_tinyxml2_diagnostic.h. \CC @rpoyner-tri for any other thoughts |
Having not actually re-read all of the sdformat parser code, I suspect we can do something very similar, or even extend/rework some of the existing urdf solution. |
I've started something like this while working on #16785 https://github.com/sammy-tri/drake/blob/sdformat_warn_unsupported/multibody/parsing/detail_sdf_diagnostic.cc |
@EricCousineau-TRI , yes, we can queue this up, unless @sammy-tri's work resolves this. |
I certainly don't mind working on it while I'm in there adding the other diagnostic stuff. Feel free to reassign to me. |
Sorry missed the ping. This issue might benefit on the completion of gazebosim/sdformat#820. Adding some examples on the current status of the
I'm a bit unsure of the scope of the issue is it to ensure that if a filename/lineno is reported then it's included in the diagnostic mechanism? is it to make sure SDFormat always reports filename/lineno? do we also want it from the errors at the |
FTR, just reflecting VC: For the "Unable to read SDF string", it would be nice to somehow make it clear that it is a clear string. Suggestion was to surround in quotes if string is only whitespace or empty; otherwise, just print string in following line. |
Resolved by #18462 |
Context: #16784 (comment)
FYI @azeey - you think this is something we can do in next ~month? (hopefully low-hanging fruit)
The text was updated successfully, but these errors were encountered: