Fix Travis CI build about framework

[peter279k]

@lablnet. After tracing Laravel framework deeply, the Hashing work in laravel/framework doesn't load any config array.

I think you should separate the ArgonHasher to different the Hashers with different Argon2 algorithm.

You should look at the hashing implementation in Laravel framework.

We should avoid loading the config because it's not related to the core framework.

The config will only effect on web application and it's zest/zest.

The Laravel framework uses the HashManager and HashServiceProvider classes to load the hash algorithm driver name from config. and these classes are for laravel/laravel.

Perhaps we can scratch this approach. My approach is as follows:

• Separate the config loading work from related core Hashing classes.
• Using the HashManager or HashServiceProvider to load config work and dispatch the current Hashing class.
  It's fine to ignore these classes in unit tests because they're the Dispatcher.
• We only work is to do unit tests for these core Hashing classes.

What do you think about that?

[peter279k]

In Laravel framework, it defines/initialize config in tests to do unit test for Config class.

You can consider the following code snippet in link:

Config test

[lablnet]

I see, you're right

the approach Mock config is right here

and you can do this by Sending PR

i am not sure but i think we can determine is code running from php unit testing
in Config class you can specify that condition to load config from mock file

[lablnet]

Yes you are absolutely right could you create a PR?

[lablnet]

Yes this work for know
But i am thinking about something like describe in #185

So we can load configs file if exists and in our get method there will be option default value
so at core level we can pass default value, is this good approach what do you think?

i am curious How laravel manage their config and passsed tests?