fix: checking for relation type existence #20167
Open
+7
−3
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.
What does it do?
I fixed an error, which happened when deleting content-type or collection in usage. Users faced error here - #19535
Code had error, because checking of existing metadata
db.metadata.get(type)
finishes with error, if metadata is not exist:Why is it needed?
Error happens when deleting component or collection in usage
How to test it?
I didn't add additional tests, current tests are passed
Related issue(s)/PR(s)
I faced this problem too - #19535