docs: correct parse-stubs section in readme (#502)
As the parse-stubs step is done automatically by `composer install` since 34d3d2030d
, we no longer need to explicitly instruct people to do it.
Note that sometimes you must parse the PHP stubs manually
pull/504/head^2
parent
ac6bce929f
commit
6dbeef63bc
|
@ -192,9 +192,6 @@ Clone the repository and run
|
||||||
composer install
|
composer install
|
||||||
|
|
||||||
to install dependencies.
|
to install dependencies.
|
||||||
Then parse the stubs with
|
|
||||||
|
|
||||||
composer run-script parse-stubs
|
|
||||||
|
|
||||||
Run the tests with
|
Run the tests with
|
||||||
|
|
||||||
|
@ -203,3 +200,7 @@ Run the tests with
|
||||||
Lint with
|
Lint with
|
||||||
|
|
||||||
composer lint
|
composer lint
|
||||||
|
|
||||||
|
The project parses PHPStorm's PHP stubs to get support for PHP builtins. It re-parses them as needed after Composer processes, but after some code changes (such as ones involving the index or parsing) you may have to explicitly re-parse them:
|
||||||
|
|
||||||
|
composer run-script parse-stubs
|
||||||
|
|
Loading…
Reference in New Issue