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
We should support named capture groups in RegEx, and then let the user tell us which groups they want to include in the title and where, with custom variables. If these are used, they should ignore the RegEx matches completely in the title output.
Problems this improvement solves
Right now, with the text:
Never Alone (Kisima Ingitchuna) ~~R$14.99~~ **Grátis** até 27/04/2023 • Epic Games Abra no navegador https://store.epicgames.com/p/never-alone-kisima-ingitchuna Abra no Launcher da Epic Games com.epicgames.launcher://store/p/never-alone-kisima-ingitchuna
It would be hard to make the title
Free on Epic Games: Never Alone (Kisima Ingitchuna)
Because it includes two parts of the input that are in reverse order. If we could use named RegEx groups it would be an easy query, something like this:
Which could make the title something like this... (not sure about how we design the API yet)
Free on $platform: $title /(?<title>.*?)~~.*(?<platform>steam|epic games)/i
Alternative solutions
The alternative is writing really complex RegExes that makes sure to not match any text and only save in capture groups. Even then, this is super hard because it's in reverse order.
The text was updated successfully, but these errors were encountered:
Describe the improvement
We should support named capture groups in RegEx, and then let the user tell us which groups they want to include in the title and where, with custom variables. If these are used, they should ignore the RegEx matches completely in the title output.
Problems this improvement solves
Right now, with the text:
It would be hard to make the title
Because it includes two parts of the input that are in reverse order. If we could use named RegEx groups it would be an easy query, something like this:
Which could make the title something like this... (not sure about how we design the API yet)
Alternative solutions
The alternative is writing really complex RegExes that makes sure to not match any text and only save in capture groups. Even then, this is super hard because it's in reverse order.
The text was updated successfully, but these errors were encountered: