Loopback 4, boolean values for additionalProperties are removed from JSON schema?

[Vladislav Stepanov]

Hi there,

Does someone know why boolean values for additionalProperties are ignored when converting JSON Schemas into a SchemaObject? The exact code I'm talking about is here:

https://github.com/strongloop/loopback-next/blob/master/packages/openapi-v3/src/json-to-schema.ts#L55

What I'm trying to do:

1. I created an "object" field which is mapped to a jsonb column in a postgresql db

2. Then I want to add some nested properties into that field and validation for it:

2.1 Option 1: add model references: if I got it right I could reference another model there but it means that I have to create a model per every level of nesting

2.2 Option 2: add JSON Schema validation for that field, the nested properties will not be publicly visible but the code is going to be pretty straightforward. And here I face the fact that I cannot restrict the schema to allow only defined properties because additionalProperties: false on my schema is just ignored

[Vladislav Stepanov]

Well, actually I can achieve it with setting additionalProperties to { "not": {} }:

http://json-schema.org/draft-06/json-schema-release-notes.html

>true is equivalent to {}, false is equivalent to {"not": {}}, but the intent is more clear and implementations can optimize these cases more easily