You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repository contains the php-parse file, which is a symbolic link to the vendor/nikic/php-parser/bin/php-parse file. It makes sense during development when the repository is the root repository and all required dependencies are installed in the vendor folder. However, when using this package normally, it causes an invalid symbolic link to exist. And this leads to problems. For example, in Windows, when you want to copy the whole project directory using xcopy /E /I repo temp:
...
repo\php\vendor\luracast\config\.gitignore
repo\php\vendor\luracast/config.travis.yml.
repo\php\vendor\luracast/config/composer.json.
repo\php\vendor\luracast/config/composer.lock.
repo\php\vendor\luracast/config/LICENSE.txt.
repo/php/vendor/luracast/config/php-parse.
File creation error - The filename, directory name, or volume label syntax is incorrect.
... and all other files cannot be copied because of this error. Problems also occur when archiving the project in ZIP, RAR, etc.
I would like you to remove this file from the repository and create a new stable tag (e.g. 2.0.3).
The text was updated successfully, but these errors were encountered:
The repository contains the
php-parse
file, which is a symbolic link to thevendor/nikic/php-parser/bin/php-parse
file. It makes sense during development when the repository is the root repository and all required dependencies are installed in thevendor
folder. However, when using this package normally, it causes an invalid symbolic link to exist. And this leads to problems. For example, in Windows, when you want to copy the whole project directory usingxcopy /E /I repo temp
:... and all other files cannot be copied because of this error. Problems also occur when archiving the project in ZIP, RAR, etc.
I would like you to remove this file from the repository and create a new stable tag (e.g. 2.0.3).
The text was updated successfully, but these errors were encountered: