build: Embed AutoCompleteRegexes as raw string literal #12244
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
instead of as resource file
mstv
commented
Mar 7, 2025
Comment on lines
-121
to
-124
| if (entryAssembly is null) | ||
| { | ||
| // This will be null during integration tests, for example | ||
| return Enumerable.Empty<string>(); |
There was a problem hiding this comment.
This comment is not true with current "dotnet test".
RussKie
approved these changes
Mar 7, 2025
gerhardol
approved these changes
Mar 8, 2025
mstv
added a commit
to mstv/gitextensions
that referenced
this pull request
Mar 9, 2025
when using AutoCompleteRegexes.Default Refs: Addendum to gitextensions#12244
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.
Fixes #12226
Proposed changes
AutoCompleteRegexes.txtas raw string literal instead of as resource file in order to be able to use them in tests, tooScreenshots
N/A
Test methodology
Merge strategy
I agree that the maintainer squash merge this PR (if the commit message is clear).
✒️ I contribute this code under The Developer Certificate of Origin.