I am aware that trailing comma is not in the JSON standard, at the same time it is accepted by other parsers like Json.net and also given in an example by Google. Maybe you want to consider it. It's a potential problem in public/integration API's when you don't control what the client sends.
Testing the lib and as a freak accident I used the JSON from: https://developers.google.com/search/docs/guides/intro-structured-data The trailing comma here after "43 g" causes an exception. JsonParsingException: 'expected:'String Begin Token', actual:'}', at offset:720'
I am aware that trailing comma is not in the JSON standard, at the same time it is accepted by other parsers like Json.net and also given in an example by Google. Maybe you want to consider it. It's a potential problem in public/integration API's when you don't control what the client sends.