Chris Johnson

This appears to be a bug in handling relative path names to the config file. If you use an absolute path (e.g. `/Users/foo/project/config.json`) it will work. I am seeing this...

I was surprised myself when it did not. Do you need an example?

Here is the option input array I'm using: ```php $this->getopt = $context->getopt([ 0 => 'v,verbose', 1 => 'h,help', 2 => 'c::', 3 => '#action?', ]); ``` I call my CLI...

I'll take a look at writing a test and PR.

I've been working on finding a fix using the above #60 test for hours now, without success. Either I'm really not understanding what's going on, or the code is seriously...

Yes, if it breaks compatibility, it'd have bump to a new major version. I'm ok with that. ;-)

I _think_ if Aura.Auth just used a compatible API (PHP interface) to its included Session class, then users of it could optionally and easily plug in Aura.Session to get its...

It appears that Aura.Session's `SegmentInterface` and Aura.Auth's `SegmentInterface` are currently 100% compatible, with Aura.Auth's being a subset of the Aura. Session's. *Aura.Auth:* ``` $ fgrep function SegmentInterface.php public function get($key,...

Aura.Session strangely does not have an *interface* definition for the `Session` class, while Aura.Auth does. However, the `Aura\Session\Sesssion` class appears to be compatible with `Aura\Auth\Session\SessionInterface`. *Aura\Auth:* ``` $ fgrep function...

A problem might be the constructors for the `Session` class. Perhaps some clever use of a Dependency Injection Container might solve this, however. **Aura.Auth**: ``` public function __construct(array $cookie) ```...