-
Notifications
You must be signed in to change notification settings - Fork 32
u3d/install: convert Windows paths to ruby paths when treating U3D_EXTRA_PATHS #388
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
u3d/install: convert Windows paths to ruby paths when treating U3D_EXTRA_PATHS #388
Conversation
|
I didn't test this :) |
9678e29 to
6f4dbed
Compare
6f4dbed to
3be4934
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not super found of that. I was thinking of tackling this as well. I would have tried the following:
File.expand_path(path)may actually work IIRC, I wanted to test this out. Plus it would be more Unix-friendly- Create a U3dCore::Helper method if expand_path doesn't work, such as the existing
U3dCore::Helper.windows_path
|
👍 I let you test&fix this then. |
437c5d1 to
0fb0a8f
Compare
|
@lacostej Cool! I was pretty sure |
💯 |
3c45367 to
c6318e7
Compare
c6318e7 to
a3e8704
Compare
niezbop
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The implementation looks food to me, but I'd rather have a little cleanup of the specs.


Pull Request Checklist
bundle exec rspecto make sure that my PR didn't break any testbundle exec rubocopto make sure that my PR is inline with our code stylePull Request Description
The documentation states that U3D_EXTRA_PATHS are windows style.
Fixes #383