Fix LocProject.json generation file finding bug #7143
Merged
Conversation
This file contains hidden or 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
riarenas
approved these changes
Mar 23, 2021
akoeplinger
pushed a commit
to akoeplinger/arcade
that referenced
this pull request
Apr 12, 2021
jonfortescue
added a commit
to jonfortescue/arcade
that referenced
this pull request
Apr 22, 2021
jonfortescue
added a commit
to jonfortescue/arcade
that referenced
this pull request
Apr 22, 2021
jonfortescue
added a commit
to jonfortescue/arcade
that referenced
this pull request
Apr 22, 2021
jonfortescue
added a commit
to jonfortescue/arcade
that referenced
this pull request
Apr 22, 2021
jonfortescue
added a commit
to jonfortescue/arcade
that referenced
this pull request
Apr 22, 2021
jonfortescue
added a commit
to jonfortescue/arcade
that referenced
this pull request
Apr 22, 2021
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 extremely silly bug was found by testing in FSharp. Validated that it doesn't break anything by testing in FSharp, SDK, and winforms.
To double check: