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

Incorrect file paths generated on Windows #36

Closed
leonelngande opened this issue Aug 30, 2019 · 5 comments · Fixed by #37
Closed

Incorrect file paths generated on Windows #36

leonelngande opened this issue Aug 30, 2019 · 5 comments · Fixed by #37
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed released

Comments

@leonelngande
Copy link
Contributor

Describe the bug
On Windows, the asset paths generated have double back-slashes (sometimes three) at the first directory level. This causes cli.test.js to fail, also user has to manually correct the asset paths generated.

To Reproduce
Steps to reproduce the behavior:

  1. Execute cli command git clone https://github.com/onderceylan/pwa-asset-generator.git
  2. cd to project root and execute cli command: npm run jest
  3. See error

Expected behavior
cli.test.js should pass

System (please complete the following information):

  • OS: windows 10
  • node version: v10.15.3
  • npm version: 6.11.2
  • cli version: 1.1.6

Screenshots
image

@leonelngande leonelngande added bug Something isn't working needs verification Bug needs to be verified with reproduction labels Aug 30, 2019
@onderceylan onderceylan removed the needs verification Bug needs to be verified with reproduction label Aug 30, 2019
@onderceylan
Copy link
Collaborator

Thanks for the issue @leonelngande! We need to fix the path issues on Windows asap.

@onderceylan onderceylan added the help wanted Extra attention is needed label Aug 30, 2019
@leonelngande
Copy link
Contributor Author

Okay! Should I look into it? Have had a look at helpers/file.js and looks like that's where the paths are generated.

@onderceylan
Copy link
Collaborator

Please, I'd appreciate that as I have to spin off a VM to inspect. Feel free to work on it.

@leonelngande
Copy link
Contributor Author

Great! On it thanks.

leonelngande added a commit to leonelngande/pwa-asset-generator that referenced this issue Aug 30, 2019
… added to icon and html content

Introduce the slash npm package to use in converting backslash paths generated for saved images to
slash paths, which are needed for generated html and manifest json content

fix elegantapp#36
leonelngande added a commit to leonelngande/pwa-asset-generator that referenced this issue Aug 30, 2019
Introduce a function to get the relative image path, replacing ternary expressions currently being
used for same functionality with it

re elegantapp#36
onderceylan pushed a commit that referenced this issue Aug 30, 2019
… added to icon and html content

Introduce the slash npm package to use in converting backslash paths generated for saved images to
slash paths, which are needed for generated html and manifest json content

fix #36
onderceylan pushed a commit that referenced this issue Aug 30, 2019
Introduce a function to get the relative image path, replacing ternary expressions currently being
used for same functionality with it

re #36
onderceylan pushed a commit that referenced this issue Aug 30, 2019
## [1.1.7](v1.1.6...v1.1.7) (2019-08-30)

### Bug Fixes

* **file.js, pwa.js, package.json:** fix Windows backslash paths being added to icon and html content ([24fef99](24fef99)), closes [#36](#36)
@onderceylan
Copy link
Collaborator

🎉 This issue has been resolved in version 1.1.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed released
Projects
None yet
2 participants