Skip to content
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

Url passed to transformUrl should be normalized #115

Open
adamreisnz opened this issue Jan 12, 2016 · 11 comments
Open

Url passed to transformUrl should be normalized #115

adamreisnz opened this issue Jan 12, 2016 · 11 comments

Comments

@adamreisnz
Copy link

On OS X, the url passed to the transformUrl function is normal, e.g. something like components/app/app.html. However, that same url on Windows becomes components//app//app.html.

It seems to be because somewhere along the line the Windows backslashes are converted to forward slashes, and for some reason an additional slash is added. This means you have to take into account when writing the transformUrl function, that the input you get is not going to be consistent across different OS's.

Is it possible to let the gulp-angular-templatecache normalize the url before passing it to the transformUrl function, so that there are no OS dependent differences?

@hung-doan
Copy link

👍
temporary solution is use path.normalize to normalize your url before return in transformUrl

@simonua
Copy link
Collaborator

simonua commented May 29, 2018

@adamreisnz, @hung-doan, is this still relevant? If so, could you create a PR, please? If not, could you close the issue, please?

@adamreisnz
Copy link
Author

This is still an issue AFAIK yes, but I'm not very interested in development for windows, just wanted to report the issue.

@simonua
Copy link
Collaborator

simonua commented May 30, 2018

@adamreisnz, I understand. Thanks for the reply. @hung-doan, would you care for a PR, please?

@simonua
Copy link
Collaborator

simonua commented Nov 2, 2018

Closing this issue due to lack of response. If this should be reopened, please provide accompanying PR.

@simonua simonua closed this as completed Nov 2, 2018
@adamreisnz
Copy link
Author

It's still an issue AFAIK, and just because the community is not interested in submitting a PR at this stage (I don't have access to windows computers in the first place), doesn't mean there hasn't been response.

@simonua
Copy link
Collaborator

simonua commented Nov 2, 2018

That's fair, and this can be viewed from different perspectives, but in order to do housekeeping on open issues, it's not uncommon to close issues that have remained open for a long time without any progress. I should mention again that I'm not opposed to reopening it at all.

@adamreisnz
Copy link
Author

True, but I think it'd be more productive to label it as "help wanted" and leave it open, so that if anyone does feel so inclined, they can pick up these issues. No one is going to sift through the list of closed issues to look for things to do, so essentially this issue is just being swept under the rug ;)

@simonua
Copy link
Collaborator

simonua commented Nov 5, 2018

@adamreisnz, good conversation. Let's go with a "help wanted" issue then. Thank you.

@simonua simonua reopened this Nov 5, 2018
@adamreisnz
Copy link
Author

Awesome, thanks for that!

@simonua
Copy link
Collaborator

simonua commented Nov 6, 2018

Yeah, you bet. Good arguments in a productive conversation. Thanks for chiming in, Adam!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants