We have found that it is pretty common (elastic/integrations#2643) to have typos in fields properties. This can be an important issue because this may create unexpected field mappings, and fixing mappings uses to bring breaking changes.

In #281 I explore the enforcement of stricter validation, but there I found that at least for the example field we would need some trade offs.