<@U5UU34LPK> yup. This is simple. I need add only `.` and `-` (internal token char) in regex and run...

# getting-started

[pyrkamarcin]

@karelpeeters yup. This is simple. I need add only . and - (internal token char) in regex and run.

[karelpeeters]

And number's don't really work, something lile (?!\d)(\w+) might be a bit closer.

[karelpeeters]

Out of interest, where are you getting these almost-json strings?

[pyrkamarcin]

From AWS Cognito 😞

[karelpeeters]

Huh that's strange. Looking trough some random docs I see well-formed json: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_AddCustomAttributes.html

[pyrkamarcin]

Yes. But there is only requests.
I have not 100% confidence of valid my response.

[pyrkamarcin]

Och. I broke this string:
eyJraWQi5iuerhteiurht-ertertert.OiI3Qnw

[karelpeeters]

(?!\d+)([\w-\.]+)

[karelpeeters]

Is fine as long as it doens't start with a number.

[karelpeeters]

Looks like (?!\d+[^\w])([\w-\.]+) is always fine, as long as there's no floats and booleans.

[pyrkamarcin]

(?!\d+[^\w])([\w-\.]+) looks perfect!

[karelpeeters]

I hope you made sure there's really no other way, because I wouldn't be happy about this simple smile

[pyrkamarcin]

Sadly yes.
I make another .replace() and finaly I got valid JSON.

[orangy]

Can’t resist 🙂 https://stackoverflow.com/a/1732454/18575

[karelpeeters]

A must-read when abusing regex!