Repository navigation
Normalize paths to avoid case-sensitivity on Windows - #451
chadlwilson merged 4 commits into
Conversation
Signed-off-by: sschulz92 <[email protected]>
Signed-off-by: sschulz92 <[email protected]>
|
@chadlwilson Any chance to get this one done including releasing it? 😄 |
|
There's always a chance 😅 This is an alternate (but preferred from your perspective) approach to your other PR? |
I wanted to keep the PR as small as possible and basically this is it. By using hte After this is done I would like to finish the other PR which is more a refactoring than a bugfix. |
Signed-off-by: sschulz92 <[email protected]>
|
@chadlwilson can you have a look on this beauty and merge it if there are no concerns? :) |
|
I’m seeing the same issue in my project as well. Could you please take a look? @chadlwilson |
|
Sorry to be so slow here, too many languages recently - took me a while to get energy back to remember how python works 😅 |
This PR is related to #445 - apparently I want to overcome an issue using Gauge with VS Code: the C drive is written in capital
C:but in VS Code some paths are written in lower casec:which causes the following stacktrace to happen:I copied the unit tests to a new branch based on master and executed them with following error:
After I cherry-picked the changes in
registry.py, the test passed on Windows (and will properly also pass on Linux using GitHub actions). I verified that the actual Gauge test scenarios (from the stacktrace above) passed too installing the SNAPSHOT version locally.Once this PR is merged, I can tackle the actual refactoring more precisely in the other Pull-Request to avoid mixed changes.
@chadlwilson maybe it is worth to release this separately also? So that this version is the bug-fix and the next might be the refactoring to load steps?