Open source feature flagging and experimentation platform for stress free deployments, measured impact, and smarter decisions.

GrowthBook Users

image.png

Anna have you tried a different, older flavour of regex? I’ve no idea which version GB supports, but I’ve had this issue with regex differences with MySQL and Python and sometimes you need to not use the new style \*s tokes. Try sticking it through <https://regex101.com/> or bard/gpt.

Hi Matt!
Thank you for the input! We will check this out!

Our developer wrote back that he tried it, and got this.
The problem is that the regex we put in, gets changed

Hi <@U01T6HCHD0A>!
Could you please help, we stuck here. Thank you!

you can enter the url without escaping the slashes, we’ll add the escaping

Hi <@U01T6HCHD0A>!
Thank you for your answear. Our developer says he tried it too, and didnt work.
Should we just take out some of the escapes then? If yes, which ones?

What we try to reach with this
`https:\/\/ingatlan.com\/(.*\/)?([0-9]+)`

Is that it begins with
<https://ingatlan.com/>
Then it includes numbers, which might come directly after the above,
or there might be a text/ before
e.g.
<https://ingatlan.com/33810996>
or
<https://ingatlan.com/xi-ker-budapest-lakas/33810996>

but after the last / there must be only numbers