You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2021. It is now read-only.
Also to add to the fact this is a bug. If you have two Modules both defined as HomeModule, one in a ModulePath and one without.
When using the ModulePath, it will always look in the Views folder first before looking for the Module Path in the root directory, so it's not possible to have two views named the same, it will always load the incorrect view for the ModulePath.
Given a module:
The route is defined as:
http://localhost/
The View is looked for in:
Views/Home/index
When using a ModulePath
The route is located by:
http://localhost/admin/
The View should be located first in:
Views/Admin/Home/index
Then
Views/Home/index
What is happening is it's trying to find the views in:
/Admin/index
What I think should happen:
When a ModulePath is defined as:
base("admin")
The View resolution should be found in the Views folder as per normal modules, the difference being that the flow is:
Is a ModulePath is defined with a forward slash prefix:
base("/admin")
Then the View resolution should be:
The text was updated successfully, but these errors were encountered: