feat(doctrine): Remove PUT & PATCH for readonly entity #7453
+257
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Good idea. |
aaa2000
force-pushed
the
feat-7019-doctrine-readonly
branch
from
7e80c37 to
610265f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When an entity is marked as readonly (via Doctrine’s [#Entity(readOnly: true)]), API Platform should automatically exclude write-related operations (PUT, PATCH) from the generated OpenAPI documentation. This aligns with Doctrine’s behavior, where readonly entities are skipped during updates but still allow creation and deletion.
Changes:
OpenAPI documentation now omits PUT and PATCH operations for entities marked as readonly.
POST and DELETE operations remain available, matching Doctrine’s semantics.