Post #3454289

@stuartmarks@mastodon.social @mehmandarov@mastodon.social Thanks for the link, I hadn't seen it! It describes exactly the same issue. I want to add though that this isn't strictly about REST, this also affects message brokers. The point of recognizing added fields and typos is valid, but that strictness could be handled with warn logs, rather than complete failure by default. In the rare case you want stop deserializing when it happens then that should be a config option. Good to see other providers have realized this.