Closed Falsal closed 9 months ago
Where is the screenshot from? Local dev? UAT? Prod?
Can you find this in the database? Where is it? How is it shown in the database?
The database holds this:
It seems to be a problem in the frontend how it is interpreting this string. Maybe the ">" is creating a problem?
After import of new data, this error is not visible in 20 tests of different tours. I will suppose it is done now, we will open this issue again if it reappears .
Front end seems to be impacted by changes in the API, after I pulled changes to API made last week , I am currently getting this (see screenshot)