Option to avoid "fixing" \ in new TaskItem() #11120
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
jeffkl
reviewed
Dec 10, 2024
JanKrivanek
approved these changes
Dec 11, 2024
rainersigwald
approved these changes
Dec 13, 2024
This was referenced Jul 28, 2025
This was referenced Aug 4, 2025
This was referenced Aug 29, 2025
This was referenced Oct 15, 2025
Closed
Open
This was referenced Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fixes #11083
Context
Sometimes
TaskItemsare not file paths, and we currently treat all of them as file paths and try to fix backslashes into slashes.Changes Made
Added an option where
TaskItemscan be created without a reference to a path, and it will not try to fix it.