Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation for types tag uses Twig types in examples instead of PHP #4403

Closed
wants to merge 2 commits into from

Conversation

drjayvee
Copy link
Contributor

Specifically, "bool" => "boolean" and "int" => "number".

This aligns the types documentation with templates.rst. See #4362

Thanks, @alexander-schranz!

Specifically, "bool" => "boolean" and "int" => "number".

This aligns the `types` documentation with templates.rst. See twigphp#4362

Thanks, @alexander-schranz!
@ruudk

This comment was marked as resolved.

@ruudk
Copy link
Contributor

ruudk commented Oct 21, 2024

The documentation is not up to date. PHPStan does properly understand number 🎉
I'll fix the docs.

See https://phpstan.org/r/24895f82-975a-4e08-b7b1-5da29d058ddd

@ruudk
Copy link
Contributor

ruudk commented Oct 21, 2024

Done:

@smnandre
Copy link
Contributor

Do you think it's worth it to update TypesTest.php and TypesTokenParser.php ?

@fabpot
Copy link
Contributor

fabpot commented Oct 23, 2024

Thank you @drjayvee.

fabpot added a commit that referenced this pull request Oct 23, 2024
…nstead of PHP (drjayvee)

This PR was squashed before being merged into the 3.x branch.

Discussion
----------

Documentation for types tag uses Twig types in examples instead of PHP

Specifically, "bool" => "boolean" and "int" => "number".

This aligns the `types` documentation with templates.rst. See #4362

Thanks, `@alexander`-schranz!

Commits
-------

f3e0a00 Documentation for types tag uses Twig types in examples instead of PHP
@fabpot
Copy link
Contributor

fabpot commented Oct 23, 2024

Not sure why Github doesn't understand this one was merged 🤷

@fabpot fabpot closed this Oct 23, 2024
@stof
Copy link
Member

stof commented Oct 23, 2024

@fabpot this happens when we squash commits but we are not allowed to push the squashed commits back to the branch from which the PR is submitted.
There is no way to mark a PR as merged when performing a squash or rebase entirely locally.

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

Successfully merging this pull request may close these issues.

5 participants