Not at the moment, but it’s something I use in VSCode, so it’s on the backlog to be brought, just low on the priority list.
Since find/replace works fine for the current use case (even if not optimal)
Since find/replace works fine for the current use case (even if not optimal)
The use case is far too niche to move engineering efforts to immediately, so it'll be prioritised when either:
- the ask quantity increases.
- when an adjacent part of the code is being improved/fixed and this could be tacked upon in the same release.
Thanks for the suggestion!