Guard against element type mismatch at document type creation #18529
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.
Prerequisites
Description
#16421 introduced guards against (and warnings for) element type mismatch for document types. Unfortunately, while the PR actually added guards at document type creation time, these guards were never actually applied 😢
This PR fixes it.
Testing this PR
You'll need to use Swagger UI to test this, as the backoffice client UI doesn't support creating inherited document types yet.
Now do the same, but with a parent element type and a child document type. The result should be the same.
You can use the following payload when testing with with Swagger UI. Remember to:
isElement
according to the test case you're executing.