Closed labra closed 2 years ago
This is due to limitations with the free shortener service, as mentioned in #26. The server should not return a 400 error in those cases, I'll look into it.
I've reduced the chance of triggering this issue. In https://github.com/weso/rdfshape-client/pull/36 I disabled the permalink option when validating data by file or when the text provided is too long to form a valid URL:
As for the possibility of showing a prettier error message, I find it difficult. Right now we're serving the front-end with express (nodejs) and, as stated here, the max request size is not something worth messing with.
Regarding the error itself, there is not much more we can do, any page will respond with an error if given a long enough URL (example).
Closing since the front-end prevents the user from creating invalid permalinks and the permalink service we're using is now our own and returns more detailed errors.
When trying to visualize some medium size RDF data like this, the permalink option doesn't seem to work.
The problem may be that the generated URL is longer than expected but if that is the case, some nice error message would be better than the current behaviour.