-
Notifications
You must be signed in to change notification settings - Fork 83
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
Path.normalize would break without the leading slash #61
base: master
Are you sure you want to change the base?
Conversation
Note, I didn't write any tests for this as I am actually not sure how to alter the relative lookup path from testing inside a node module. Would love for someone to enlighten me. Also, the master branch has some failing tests, FYI. |
I can definitely corroborate that this is broken. Strangely enough, it worked fine when lifting locally but was unable to resolve the path when deployed to a server. I'm not sure what would cause that to happen...must have something to do with changes that occur from Sails' automatically generated "production" environment? |
Subscribe.
|
Added your test. It does fail. |
Changes Unknown when pulling b509aef on senica:jade-path-fix into * on waterlock:master*. |
1 similar comment
Changes Unknown when pulling b509aef on senica:jade-path-fix into * on waterlock:master*. |
From my point of view this test shouldn´t be in the test suite. It was only for local checking :) |
I put it there more for the project maintainer to check on their side as they haven't been quick in resolving this. |
In utils, if the leading slash was gone from the path.normalize when rendering the template path, it would look in the wrong location for the template and break the sending of emails.