docs: remove config keys deleted in 5.0, document %param% resolution - #2334
Merged
Merged
Conversation
soyuka
added a commit
to soyuka/doc
that referenced
this pull request
Sep 12, 2026
`Configuration.php` on upstream/main no longer exposes this key; Link security is unconditional since api-platform/core#8367. Matches the phrasing used in api-platform#2334 (core/subresources.md).
2 tasks
soyuka
force-pushed
the
docs/remove-5.0-deleted-config
branch
from
September 13, 2026 07:43
c756d30 to
e32bfd6
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
api-platform/core#8367(e22e74464),verified absent from
src/atupstream/mainof api-platform/core:validator.query_parameter_validation(core/configuration.md)resource_class_directories(core/configuration.md)graphql.graphql_playground(core/configuration.md)http_cache.invalidation.varnish_urls— renamed tourls(core/configuration.md)enable_link_security(core/subresources.md) — Link security is now always enabledapi-platform/core#8284(826e847b6):%app.param%now resolves inside YAML/XML/attributeresource configuration (Symfony only), verified against
ContainerParameterResourceMetadataCollectionFactoryand the YAML/XML extractors.Notes
xkeywas flagged by the audit as removed by #8367 too, but this is not accurate for what thedocs document: the deprecated top-level
http_cache.invalidation.xkey.gluebundle option wasindeed removed, but the docs only ever documented the resource-level
defaults.cache_headers.invalidation.xkey.glue, which is still read byApiPlatformExtension::registerCommonConfiguration()and still backed byApiResource::$cacheHeaders.No change made there.
core/dto.md(ObjectMapperProcessor→ObjectMapperInputProcessor/ObjectMapperOutputProcessor)is intentionally left untouched:
api-platform/docs#2321(open against4.3) already makes thisexact class-split edit at those lines, plus more, and will flow into
mainthrough the branchmerge-up.
core/filters.md:716also documentsenable_link_security(forReadLinkParameterProvider) butis out of scope for this PR/branch; left for the agent owning
core/filters.md.