Closed timfsw closed 12 months ago
@ngan any thoughts on this PR?
If I understand the problem we are trying to solve, then another solution to this PR would be to change the behavior to make frontend/authentication
be the auto-magic engine name instead of authentication
I've needed a possibility to set a custom engine namespace to create different engines with same package folder name.
Currently the following package structure creates the same engine
Authentication::Engine
Now it's possible to set a custom engine name to prevent this issue.
This will generate the following engines:
Backend::Authentication::Engine
andFrontend::Authentication::Engine
I think it is better to specify the name explicitly instead of generating the package name based on the folder structure.