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
From a short look at the Drogon source code currently all CSP files have to reside in one directory. It is not possible to structure them otherwise. This is OK for smaller projects, or projects where you rely on REST APIs instead of a more “traditional” backend with template generation, but it can get confusing very fast when you have more than a dozen pages.
Ideally it would be possible to reference views from subdirectories of the configured views directory. Imagine a subdirectory called components or layouts which holds together building blocks for a traditional HTML website. Whenever I would reference components/AudioPlayer from my Album view (CSP file to be more precise) the framework would descend into subdirectories and also handle this case.
The text was updated successfully, but these errors were encountered:
From a short look at the Drogon source code currently all CSP files have to reside in one directory. It is not possible to structure them otherwise. This is OK for smaller projects, or projects where you rely on REST APIs instead of a more “traditional” backend with template generation, but it can get confusing very fast when you have more than a dozen pages.
Ideally it would be possible to reference views from subdirectories of the configured views directory. Imagine a subdirectory called
components
orlayouts
which holds together building blocks for a traditional HTML website. Whenever I would referencecomponents/AudioPlayer
from myAlbum
view (CSP file to be more precise) the framework would descend into subdirectories and also handle this case.The text was updated successfully, but these errors were encountered: