Update postcode field to GDS guidance about coronavirus-dashboard-frontend-server HOT 2 CLOSED

There are two issues here.

1. I agree that there needs to be an example. It used to have one, not sure why or when it was removed.
2. I will not be allowing invalid postcodes. The service has been tested with 100s of users and is used by million each week. Processing a variety of postcodes would bypass the CDN cache and the API cache - i.e. 2 of the 3 caching layers - and put unnecessary pressure on the service. Considering that the service sustains between 50 and 70 million requests a day, it stands to reason to take measure to mitigate the traffic in anyway possible. Generic guidelines do not usually cater for all circumstance.

I do not usually respond to such issues on GitHub as they are not specifically related to development. However, I am doing so on this occasion because you have taken the time to provide a nicely structured issue, so I shall return the courtesy by taking note of your kindness.

Thank you.

PS: We regularly work with the GDS, because as I am sure you have noticed, our design does not entirely conform to their guidelines.

from coronavirus-dashboard-frontend-server.

Thanks for your response. I'm a bit confused by the response to my comment about html5.
I wrote: '1. The postcode field uses html5 validation. GDS guidance says: "Turn off HTML5 validation"'
You wrote: '1. I agree that there needs to be an example. It used to have one, not sure why or when it was removed.'

My comment wasn't about an example, it was about html5 validation.
Trying to help.

from coronavirus-dashboard-frontend-server.