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

"Unable to read SHACL definition" does not give any error indication #243

Open
roper79 opened this issue Feb 4, 2022 · 3 comments
Open

Comments

@roper79
Copy link

roper79 commented Feb 4, 2022

To reproduce
SHACL Shapes -> Create Shape, write/paste in definition, hit "Create Shape"

Expected behavior
In case "Unable to read SHACL definition", a reason should be displayed.

Context

  • FDP version: 1.12.0

2022-02-04_16-02-1643989828

@kburger
Copy link
Contributor

kburger commented Feb 23, 2022

Hi @roper79, are you able to share a minimal example of a shape definition that produces this error? You are right of course that the user feedback should be more detailed, I'll put this issue on the backlog. Thanks for reporting.

@roper79
Copy link
Author

roper79 commented Feb 23, 2022

It seems that any syntactic error in SHACL results just in this message. Would it be possible to explain the parsing error in the UI?

@kburger
Copy link
Contributor

kburger commented Feb 23, 2022

Clear, something we need to take up into the testsuite. Assuming the underlying library supports a more detailed error message (don't know by heart if it does), we can for sure pass that back to the client view. We'll look into it.

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