hoaproject / cli Goto Github PK

From @Hywan on November 10, 2014 11:9

Please, see point 5 of http://php.net/reference.pcre.pattern.differences. Consequently, we are not able to write something like: s/-(.)/\u\1/ to transform foo-bar into fooBar. We have to implement it by ourselves.

• \U,
• \u,
• \L,
• \l,
• \E,
• \e.

Two locations: either in the zFormat or in Hoa\Regex (we would create a new “preg_replace”-like implementation). I would go for Hoa\Regex but it will create a dependency between Hoa\Core and Hoa\Regex which must not happen (in this way). However, supporting it in all regular expressions used in Hoa would be great… So I propose to (1) implement it in the zFormat, and then (2) in Hoa\Regex.

Thoughts?

Needed to continue hoaproject/Core#56 (comment).

Copied from original issue: hoaproject/Core#57

hoa help and derivates like hoa help command would be really useful to document commands and their options, like for example pragmas ( hoaproject/Compiler#52 ) for Compiler.

hoa help would then use man if available, and fallback to other format.

I noticed Cli/Bin/Welcome.php use \n char for printing new line in the Console.
The Best Practice is PHP_EOL, as DIRECTORY_SEPARATOR for /.
It causes some unexpected issues while we share our code to Windows users ;)

Progression:

• Close jubianchi/hoaproject-cli#1,
• Close hoaproject/Core#70,
• Close hoaproject/Core#91,
• Register on Packagist.

• Hoa\Devtools,
• Hoa\Test.

From @Hywan on November 9, 2014 14:25

We just remove dashes in command name. For example, for the Hoa\Devtools\Bin\Requiresnapshot command, we can write:

$ hoa devtools:require-snapshot

instead of

$ hoa devtools:requiresnapshot

The first one is far more readable.

Of course, we can also write:

$ hoa devtools:r-e-q-u-i-r-e-s-n-a-p-s-h-o-t--------

and it will work.

Pro: help to read long commands.
Con: several “names” for the same command, which is not… good :-/.

Thoughts?

/cc @hoaproject/hoackers

Copied from original issue: hoaproject/Core/pull/56