latest alphas now include full regex support in VL.
so have a look at Replace [Text.RegularExpressions]
but then…maybe you don’t even need a regex at all and can also do with the ordinare replace? depends a bit on your clarified usecase…
Thanks @joreg, it was the Unescape node that I was most in need of but all of these RegEx nodes are going to come in handy, allowing for more powerful string manipulation, with a little more knowledge.
I was going to say they should be both processes and operations, checked and my wishes were already answered, but I’ll leave it here for perspective.
The only thing I’m wondering is whether they should be processes or operations. As processes they cache the output, which makes them lighter on a program since they’re only called on changes to the inputs, but on the other hand they can’t be used in stateless scenarios, like delegates, and I guess records.
But then as someone types in a pattern it will throw an error on the incomplete expression. In a cache this is momentary, just a flicker on each key stroke (is/could auto-updated string input be an optional setting?), but in an operation, I suppose the error keeps getting raised until the expression is written correctly.
So maybe the RegEx nodes should be available in both flavours, putting the operation versions in the advanced category.