Skip to content

Bug with set() functions #1072

Closed
Closed
@Seb33300

Description

@Seb33300

Hello,

On a Laravel project, I am using deployer where a set() function is defined to setup the global configurations.

Since PHP-Parser version 5.4.0, it seems like something wrong happened with that set() function, breaking my Pint (PHP-CS-Fixer for Laravel) pipelines in my project.

I created a reproducer in the Pint project here: laravel/pint#353

This seems to be related somehow to latest changes in PropertyHook where I can see some set hardcoded?
See: 6478c5a#diff-7b34ed55e32983d7ed56a09fc70ba016f0b84cf024c8062b8dcb2682157edca4

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions