A post doing the rounds among developers this month covers TypeScript null safety, which is a way of getting the computer to catch mistakes before your visitors do. TypeScript is a stricter version of JavaScript, the language most websites are built with. The argument in the piece is that turning on the safety checks is not enough on its own. Your code also has to explain why a piece of information is missing.
That sounds abstract. It is not. JavaScript treats three very different situations identically: a field that was left empty, a system that failed to answer, and a value nobody has filled in yet. All three come back as nothing. If the code cannot tell them apart, it usually handles them all the same way, which is to say badly.
You have almost certainly seen the result. A product page showing a price of nothing at all. A booking confirmation that greets someone as "Hi ," because the first name field was optional. A testimonial slider that renders an empty grey box. A contact form that appears to submit but quietly loses the message because the email service did not respond and nothing told the visitor. None of these look like technical problems to a customer. They look like carelessness.
The piece also mentions migrating these checks on gradually, file by file, rather than all at once. That matters if you have an older site. A developer does not have to rebuild everything to start closing these gaps. They can tighten the parts that touch your money and your enquiries first, and leave the rest.
So this changes nothing about your site today. Nobody needs to act on a developer blog post. But it does point at a category of fault worth checking for yourself.
What to do
Spend ten minutes trying to break your own site. Submit a contact form with the optional fields empty. Look at a product or service page that is missing an image or a price. Check what happens if you fill in only half a form and hit send.
If you find a blank box, an empty greeting or a form that swallows a submission without saying anything, write it down and send the list to whoever maintains your site. Ask what the site does when information is missing or a connected service does not answer. That is the useful question here.
Reported by:
