Avoid uncaught fatal errors in REST API if vocabulary ID not found #1231
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1170
This is a similar fix as #1215, but for the REST API.
For an URL like this: http://localhost/Skosmos/rest/v1/koko2/data?format=text/turtle
(note that there is no vocabulary with the id
koko2
defined in config.ttl)it prevents uncaught fatal errors like this:
Instead a 404 error is produced, like this: