Fixed production check, removed assertion #11273
Merged
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.
Scope & Purpose
When orphan collections were provided to the gharial API as an array, but the elements weren't strings, in maintainer mode an assertion would trigger. The production check wasn't active, however, and would have led to a generic velocypack error.
This remove the assertion (because it can be triggered by using an external API wrongly), and fixed the production check that should have thrown a meaningful exception (but didn't).
Testing & Verification
This change is trivial. It removes a maintainer-mode assertion, and adds a more helpful error message in production.