Double quotes no longer working as intended
See original GitHub issueIt seems to be picking up hits as if a wildcard is implied between words.
Example: I search "grenade launcher reserves"
, and in addition to the expected results it finds hits with Grenade Launcher Scavenger (Grenade Launchers get bonus reserves…) but without Grenade Launcher Reserves.
I suspect this may be related to https://github.com/DestinyItemManager/DIM/pull/3386.
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (11 by maintainers)
Top Results From Across the Web
C#, escape double quote not working as expected
You need to make this a verbatim string to use the "" as an escape @"//*[@id=""yfs_j10_a""]". For a normal string literal you need...
Read more >Need to press quotes and double quotes twice in Windows 10
Pressing a quote - or double quote - does not appear to do anything. ... then delete the USA language - and the...
Read more >Quotes When Nothing Is Being Quoted | MLA Style Center
Authors often use quotation marks when nothing is being quoted. The marks may indicate irony, skepticism, derision—as such, they are sometimes ...
Read more >Is Google results page no longer showing the "exact term ...
Only the phrase in double quotes will be searched exactly. The Verbatim search is [ "show the exact term" "in" "the" "results" "page"...
Read more >GREP "Any Double Quotation Marks" wildcard not working as ...
It seems to be the "Any Double Quotation Marks" wildcard that is broken because replacing that with alternatives will work. Replacing with "Left ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That implies that perk:“grenade launcher reserves” is really just perk:grenade perk:launcher perk:reserves
That is definitely not expected. I’m with the OP. This is a bug that should be fixed.
Agree with @philkernick. Posted up a fix at https://github.com/DestinyItemManager/DIM/pull/3484.