d4e8166927
This PR was merged into the 3.4-dev branch. Discussion ---------- [config] Add abbitily to deprecate a node | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | no | New feature? | yes | BC breaks? | maybe | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | https://github.com/symfony/symfony-docs/pull/7794 For BC breaks, I don’t know if modifying the Xml and Yaml dumper output is considering as a BC break (it’s just a comment). Commits -------31d2250f4c
[config] Add abbitily to deprecate a node3b6442f8b2
feature #23947 [Translation] Adding the ability do load <notes> in xliff2.0 (Nyholm)b0cdb53d67
[Translation] Adding the ability do load <notes> in xliff2.0
2.4 KiB
2.4 KiB
CHANGELOG
3.4.0
- added
setDeprecated()
method to indicate a deprecated node
3.3.0
- added
ReflectionClassResource
class - added second
$exists
constructor argument toClassExistenceResource
- made
ClassExistenceResource
work with interfaces and traits - added
ConfigCachePass
(originally in FrameworkBundle) - added
castToArray()
helper to turn any config value into an array
3.0.0
- removed
ReferenceDumper
class - removed the
ResourceInterface::isFresh()
method - removed
BCResourceInterfaceChecker
class - removed
ResourceInterface::getResource()
method
2.8.0
The edge case of defining just one value for nodes of type Enum is now allowed:
$rootNode
->children()
->enumNode('variable')
->values(array('value'))
->end()
->end()
;
Before: InvalidArgumentException
(variable must contain at least two
distinct elements).
After: the code will work as expected and it will restrict the values of the
variable
option to just value
.
- deprecated the
ResourceInterface::isFresh()
method. If you implement custom resource types and they can be validated that way, make them implement the newSelfCheckingResourceInterface
. - deprecated the getResource() method in ResourceInterface. You can still call this method on concrete classes implementing the interface, but it does not make sense at the interface level as you need to know about the particular type of resource at hand to understand the semantics of the returned value.
2.7.0
- added
ConfigCacheInterface
,ConfigCacheFactoryInterface
and a basicConfigCacheFactory
implementation to delegate creation of ConfigCache instances
2.2.0
- added
ArrayNodeDefinition::canBeEnabled()
andArrayNodeDefinition::canBeDisabled()
to ease configuration when some sections are respectively disabled / enabled by default. - added a
normalizeKeys()
method for array nodes (to avoid key normalization) - added numerical type handling for config definitions
- added convenience methods for optional configuration sections to
ArrayNodeDefinition
- added a utils class for XML manipulations
2.1.0
- added a way to add documentation on configuration
- implemented
Serializable
on resources LoaderResolverInterface
is now used instead ofLoaderResolver
for type hinting