Closed zimme closed 7 years ago
@zimme i believe you if you say this fixes it, but i can't for the life of me see why
I believe it's the order of notFoundTemplate
and noRoutesTemplate
.
The only difference here is that we only check if any routes are defined if we don't have a notFoundTemplate
defined.
I'll test more later today, to verify the fix.
@zimme are you making your changes in a locally cloned version of the package?
Yes
how weird is this... the package from atmosphere is loading the templates/ folder even though none of it is in package.js
... but it doesn't happen if the package is loaded locally
I believe it has to do with the modules system, can't remember where but I thinnk I remember reading that all package files are evaluated to be able to support the modules api or was it lazy loading
but does that account for the difference in behavior between local and atmosphere-installed packages?
oh i think i get it
This should fix #1561. It needs to be verified because I’ve only tested that the error in #1561 doesn’t happened and not verified that the logic for noRoutesTemplate actually work.