TypeCoercion like ajv about fast-json-stringify

[Uzlopak]

const fastJson = require('fast-json-stringify')

const stringify = fastJson({
  title: 'Example Schema',
  type: 'object',
  properties: {
    boolean: {
      type: 'boolean'
    }
    }
})

console.log(stringify({
    boolean: "false"
}))

results in "{\"boolean\":true}"

awesome

[jsumners]

To what end? AJV is coercing JSON into JavaScript natives. FJS is converting JavaScript natives into JSON.

[ivan-tymoshenko]

Not a good example IMHO. With the same result, you can complain about the js standard.
!!"false" === true

but I also don't like some types coercions that we have. The question is what should we do in this case?

• throw an error
• return { boolean: "false" }
• return { boolean: false }
• return { boolean: true }
  return {}

[Uzlopak]

The risk that I see here is about diverging behaviour between ajv and fsj. Then we have some cases were ajv validates as valid and fsj maybe throws or serializes it differently. Also we potentially need to coerce the vaues if we want to process them for stuff like const and enum. If we want to go that way.

[Eomm]

I'm pro to good coercion default and not throwing.