More explicit error message when corpus_id is not set in environment
Compare changes
There are no changes yet
No changes between version 1 and version 1
To avoid the ugly 500 errors that env get when they try to use API endpoints with corpus_id=None
.
There already was a warning but this one is more explicit.
No changes between version 1 and version 1