xwp
DEV_LIB_SKIP documentation
In the docs it say to use DEV_LIB_SKIP=phpunit git commit to ignore phpunit, but that fails because the git commit portion doesn't seem accurate. Shouldn't it just be DEV_LIB_SKIP=phpunit?
When you prefix a shell command with an environment variable in that way, the environment variable is set during the life of that one command and then is removed. In other words:
$ DEV_LIB_SKIP=phpunit
$ git commit
(not running phpunit)
$ echo $DEV_LIB_SKIP
phpunit
Whereas:
$ DEV_LIB_SKIP="nothing!"
$ DEV_LIB_SKIP=phpunit git commit
(still not running phpunit)
$ echo $DEV_LIB_SKIP
nothing!
Similarly, for setting NODE_ENV when running node: https://stackoverflow.com/a/9204973/93579
That makes sense but is not clear. The context in which it’s being used is likely in the .dev-lib file not in the command line. So I could see it confusing people.
The context in which it’s being used is likely in the .dev-lib file not in the command line.
@valendesigns Could you please elaborate on that? Are you saying that setting DEV_LIB_SKIP in .dev-lib doesn't work? Or should we just include an example of DEV_LIB_SKIP in the Environment Variables section of the readme?
I’m suggesting we add an example somewhere for using it in the environment file because that’s the context it’s being spoken about. However, the example we show is for the command line and would confuse someone that didn’t know better.