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

Modules namespaces and routes #65

Open
ZeoNish opened this issue May 26, 2022 · 5 comments
Open

Modules namespaces and routes #65

ZeoNish opened this issue May 26, 2022 · 5 comments
Assignees
Labels

Comments

@ZeoNish
Copy link

ZeoNish commented May 26, 2022

How to use namespace Admin/Module_name and User/Module_name ?

folder routes not auto use ... :-(

image

Admin/routes/web.php Work (Module auto use only this path)

Admin/Test/routes/web.php Not Work

@ZeoNish ZeoNish added the bug label May 26, 2022
@ZeoNish ZeoNish changed the title Modules namespaces Modules namespaces and routes May 26, 2022
@ZeoNish
Copy link
Author

ZeoNish commented Jun 4, 2022

no idea?

@Artem-Schander
Copy link
Collaborator

Hi @ZeoNish 👋
Sorry for the late reply.
The routes are not getting registered because the your modules seem to be nested. Modules need to be placed right into the Modules directory. There is no recursive discovery for modules.

@ZeoNish
Copy link
Author

ZeoNish commented Jun 7, 2022

Hi @ZeoNish 👋 Sorry for the late reply. The routes are not getting registered because the your modules seem to be nested. Modules need to be placed right into the Modules directory. There is no recursive discovery for modules.

Thx. I will think about how to get how to implement it for me.

@ZeoNish
Copy link
Author

ZeoNish commented Jun 8, 2022

maybe it will be possible to add a parent for the module folder through the config file of the module itself?

Thus, you can specify in which parent directory this module is located and register it from this directory.

Can you help with that?

@Artem-Schander
Copy link
Collaborator

You could look into the Change The Structure part.
But I think this is not exactly what you want.
The main problem with custom paths for different modules is the Separate Config File In A Module. It won't be loaded since there is not recursive discovery.

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

No branches or pull requests

2 participants