Currently, this is causing some processes to crash in localhost, but it's not a problem when deployed. Therefore, it's not a critical priority, but turning these IDs into URL-safe would be beneficial to avoid future surprises.
@carcruz can you confirm the . are the offending characters?
As reported by @carcruz, some study identifiers derived from the eQTL catalogue are not URL-safe.
For example:
https://ot-platform-partner.netlify.app/study/Sun_2018_aptamer_plasma_TNFRSF1A.2654.19.1..1
Currently, this is causing some processes to crash in localhost, but it's not a problem when deployed. Therefore, it's not a critical priority, but turning these IDs into URL-safe would be beneficial to avoid future surprises.
@carcruz can you confirm the
.are the offending characters?