You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this should be considered a bug or a feature request but:
I am trying to replace a string in my .csproj-file (interpreting it as xml). My file contains this piece: <ItemGroup> <Folder Include="wwwroot\" /> </ItemGroup>
But even if my string exists in the file, comby cannot find it if it appears after the occurrence of \".
Reproducing
Here we can see that it will not replace the second ItemGroup:
Expected behavior
It should replace the specified string after the occurrence of \".
Additional context
I would think that the backslash before the quotation mark likely escapes the quotation, and the whole .xml from there and onwards is corrupted. However, this seems to be a valid format in an .csproj-file, which makes comby impractical to use in certain scenarios. To support this scenario would be of great value when developing in .Net.
The text was updated successfully, but these errors were encountered:
Describe the bug
Not sure if this should be considered a bug or a feature request but:
I am trying to replace a string in my .csproj-file (interpreting it as xml). My file contains this piece:
<ItemGroup> <Folder Include="wwwroot\" /> </ItemGroup>
But even if my string exists in the file, comby cannot find it if it appears after the occurrence of
\"
.Reproducing
Here we can see that it will not replace the second ItemGroup:
Expected behavior
It should replace the specified string after the occurrence of
\"
.Additional context
I would think that the backslash before the quotation mark likely escapes the quotation, and the whole .xml from there and onwards is corrupted. However, this seems to be a valid format in an .csproj-file, which makes comby impractical to use in certain scenarios. To support this scenario would be of great value when developing in .Net.
The text was updated successfully, but these errors were encountered: