More explicit error message when corpus_id is not set in environment
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.
Merge request reports
Activity
requested review from @babadie
assigned to @yschneider
Please register or sign in to reply