Adding in setup scripts for Windows powershell users #867
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
My guess is the fixtures aren't setup to handle switching formats since they are statically generated. The weird thing though is why do the slashes go both directions? It says |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds in the next step to Windows compatibility. When you generate a Lucky app on Windows, it will now generate PowerShell scripts for you to run making the flow feel similar to mac/linux.
Full disclaimer... I used AI to translate bash to powershell then followed it up with lots of stackoverflow posts 😂 I'll try to run this on an actual Windows machine to verify, but I'm just getting the PR up so we can poke around with it.