New schema save fails about horreum

[johnaohara]

{BEARER_TOKEN} is a correct token, I just omitted it from the output

[rvansa]

Are you sure you're running latest version 59a2b27 ? I've just tried to create a new schema in scalelab and it worked without issues.

[johnaohara]

Yes, I am running;

commit 59a2b27e5fe182a349bb9134dfe40a24333d2eb0 (HEAD -> master, origin/master, origin/HEAD)
Author: Radim Vansa <[email protected]>
Date:   Wed Apr 29 11:46:39 2020 +0200

[rvansa]

Okay, I can reproduce with this request (not from UI), investigating...

[rvansa]

It seems this is a bug in org.eclipse.yasson when deserializing false into custom object; the parser mistakenly jumps one level down in the object and therefore your JSON is interpretted as

{
   "name": "...",
   "uri": "...",
   "description": "...",
   "schema": {
      "owner": "...",
      "access": "...",
   }
}

[rvansa]

I've filed quarkusio/quarkus#9111

Have did you get the schema: false in the UI? I get that when I explicitly change the contents of the text area to false, but if I wipe it out completely it sends null.

[johnaohara]

The contents of the text area was a json schema, will try with an empty schema and see what happens

[rvansa]

Closing here as it doesn't seem to be fixable in Horreum/yaup at this moment. Please reopen if you figure out when does UI pass false for schema.