[BUG] parenthesis inside the foundLocation and hint fields causes data to be truncated

[KenEucker]

Describe the bug
When adding locations or hints that contain the values ( or ), in any combination, have the potential to break how data is stored for these fields.

To Reproduce
Steps to reproduce the behavior:

1. Submit a foundLocation with a ( or pair (...)
2. Submit a hint with a ( or pair (...)
3. Observe the data lost within the hint and foundLocation fields

Expected behavior
For these characters to not break the fields when included.

Screenshots

Additional context
I think it would be possible to improve the regular expressions that the biketag-api uses to be able to support parenthesis within the hint/foundLocation. If someone wants to help with this, you can look at the regular expressions that take this information and put it into/pull it from the singular title or description fields.

biketag-api/src/common/expressions.ts

Line 28 in 0053c3a

export const getHintFromTextRegex = new RegExp(/(?:hint:\s*?)([^)]*)/i)

Used here:

biketag-api/src/imgur/helpers.ts

Line 454 in 0053c3a

hint = getHintFromText(mysteryImageDescription)

And here is where the found description is built (using the foundLocation field):

biketag-api/src/common/getters.ts

Line 453 in 0053c3a

export const getImgurFoundDescriptionFromBikeTagData = (

And here is where the mystery description is built (using the hint field):
https://github.com/KenEucker/biketag-api/blob/0053c3aea51dee8c3d79a9e557323d595fcaa449/src/common/getters.ts#L485C14-L485C55

[KenEucker]

🎉 This issue has been resolved in version 3.1.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀