Fix display (and storage?) of `paymentDetails` field
Opened this issue · 0 comments
ob6160 commented
The paymentDetails field in the database is a free-form string.
This results in the UI reflecting its value in peculiar ways when it is not set to a sensible value: https://www.toiletmap.org.uk/loos/723ae70bd0e270a207b535a3, https://www.toiletmap.org.uk/loos/2f49a8a69efd09c6e9702876
Is there a better way we could store this information?
How could can we improve the quality of the data that we have?