Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for non-standard model directory path for DDD Laravel Sites #28

Closed
ejntaylor opened this issue Mar 10, 2020 · 3 comments
Closed
Labels
enhancement New feature or request
Milestone

Comments

@ejntaylor
Copy link

This might be too edge case, but I recently started using a Laravel boilerplate which places the Models inside a non-standard location (src/App/) due to using Domain Driven Design pattern..

Any ideas on supporting a site structure like this? Thanks

@mtolhuys
Copy link
Owner

Hi @raisonon , support for this is coming very soon actually. Top of the list right now.

It will be set through the config where you can point to multiple paths through an array.

@mtolhuys mtolhuys added the enhancement New feature or request label Mar 10, 2020
@mtolhuys mtolhuys added this to the 0.10.0 milestone Mar 10, 2020
@mtolhuys
Copy link
Owner

mtolhuys commented Mar 10, 2020

@raisonon you could try it out with 0.10.0.

config now:

'model' => [
    'namespace' => 'App\\',
    'paths' => [
        app_path(), \\ Add any path you want the mapper to scan
    ],
],

@cord
Copy link

cord commented Mar 12, 2020

Reading from a custom path works, however when I try to add a field the POST to /schematics/models/edit
fails with Exception
"message": "Cannot replace non-existing $fillable",
when hitting the save button.

Drag & drop to sort the new field does not work (can't drop in the list of existing fields)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants