Unable to send message with glee when payload is an object with an allOf of two or more objects about glee HOT 5 CLOSED

I would think that it's against the purpose of using these kinds of tools. I want to be able to reuse objects as much as possible, instead of implementing them over and over. These examples were simple, but in reality I have numerous big objects that are used tens of times in different messages. The only caveat in this case is that I want to have the message fully defined, and not allow any additional properties in any part of it.

But of course, it's up to you, I just thought I should report it :)

from glee.

@dankar, I think I spotted the issue in your schema. The problem is with using allOf and setting additionalProperties: false at the same time. Here's why:

• allOf is strict: With allOf, your message has to match both schemas.
• No extra properties allowed: That additionalProperties: false setting makes things tricky because it means absolutely no other properties can exist.

Your schemas are fighting each other in a paradox.

Change additionalProperties to true in one of your schemas. That'll make things a bit more flexible and should fix the error.

Let me know if that works! 😊

from glee.

@KhudaDad414 Thank you for your answer. I'm then a bit unsure of how to specify what I want: I do want the message to contain all of those objects, but absolutely nothing else.

Is it then not possible to specify that?

from glee.

I guess the best bet would be to combine your schemas into one schema. something like:

{
  "additionalProperties": false,
  "title": "setParamResult",
  "type": "object",
  "required": [
    "id",
    "valueString"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "valueString": {
      "type": "string"
    }
  }
}

if this is not a choice then I am not exactly sure if it's possible with allOf.
I am closing the issue for now.

from glee.

@dankar, you are correct. this is a limitation. but since we are using JSON Schema there is nothing we can do to address this issue. you can open an issue in the JSON Schema and if they change things things are going to work here automatically.
All I want to say is there there is nothing that we can do here.

from glee.