Skip to content

fix(metadata): parse YAML booleans and input/output arrays correctly - #8761

Open
Maxcastel wants to merge 2 commits into
api-platform:5.0from
Maxcastel:fix/yaml-scalar-types
Open

Maxcastel wants to merge 2 commits into
api-platform:5.0from
Maxcastel:fix/yaml-scalar-types

Conversation

@Maxcastel

Copy link
Copy Markdown
Contributor
Q A
Branch? 5.0
License MIT

Two small YAML parsing issues:

  • booleans used a loose in_array(), so any non empty string was true: paginationEnabled: 'false' (or a container parameter resolved to "false") enabled the pagination. They now use filter_var(FILTER_VALIDATE_BOOLEAN), yes/on are still true.
  • input: {class: App\Dto\BookInput, name: BookInput} became the string 'Array', the array is now kept like for mercure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant