Allow defining default namespaces as an array

[spawnia]

• Added or updated tests
• Added Docs for all relevant versions

Related Issue/Intent

Resolves #438
Resolves #439

Changes

From a user perspective, default namespaces can now be defined as singular strings or arrays. See:

    /*
    |--------------------------------------------------------------------------
    | Namespaces
    |--------------------------------------------------------------------------
    |
    | These are the default namespaces where Lighthouse looks for classes
    | that extend functionality of the schema. You may pass either a string
    | or an array, they are tried in order and the first match is used.
    |
    */
    'namespaces' => [
        'models' => ['App', 'App\\Models'],
        'queries' => 'App\\GraphQL\\Queries',
        'mutations' => 'App\\GraphQL\\Mutations',
        'interfaces' => 'App\\GraphQL\\Interfaces',
        'unions' => 'App\\GraphQL\\Unions',
        'scalars' => 'App\\GraphQL\\Scalars',
        'directives' => ['App\\GraphQL\\Directives'],
    ],

Breaking changes

Nope, existing configurations work as before.

[spawnia]

@chrissm79 can you please change the StyleCI setting so it commits the fixes automatically? That would prevent this merge conflict right now and make it so i do not have to go in and fix stuff manually.

[chrissm79]

@spawnia It's already set to do so. It took a minute for it to push a commit on my PR but it did so automatically

[spawnia]

Hm, maybe it does not work for branches in a different repo?

[chrissm79]

Current StyleCI setting

[chrissm79]

Could be, it only took a minute on my PR and the branch was created in this repo

[spawnia]

I read in the StyleCI docs, i think they will only commit fixes when merging the PR.

For this particular case, i think i will try to manually apply the patch

[chrissm79]

Nice work @spawnia 👍