Closed Rock-it-science closed 2 years ago
If anyone else has this issue, a temporary solution is to use v1.0.0 which was before the query parameter feature was added.
@Rock-it-science
Thanks for reporting back! I've fixed the parser for the two cases listed below and released it as v1.12.3, so please give it a try. If it's not fixed in your case or if you find other cases of mistakes, please let me know 😄
Looks like this fixed my issue, thank you!
I am a new user of this extension and have been loving it so far, but have noticed that the query parameter feature causes issues for strings (regex strings for example) where '@' and '?' should remain as those characters, and not trigger query parameters. Thanks!