Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[Yaml] ~ is not interpreted as null when used as array key #23664

Copy link
Copy link
Closed
@ivoba

Description

@ivoba
Issue body actions
Q A
Bug report? yes
Feature request? no
BC Break report? no
RFC? no
Symfony version 3.3.5

When using ~ as array key its interpreted as string "~" since i upgraded to symfony 3.3.
Before it was interpreted as null resp. "".

As it is in Yaml spec it should be interpreted as null even as key, i suppose:
http://www.yaml.org/type/null.html

Example:

my_service:
  class: SomeClass
  arguments:
    -
     ~: 'default'
     key: 'value'

Arguments results in:

array:2 [▼
"~" => "default"
"key" => "value"
]

Expected would have been:

array:2 [▼
"" => "default"
"key" => "value"
]

Is this intended behaviour?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.