5

{
"$schema": "http://json-schema.org/draft-04/...#",
"type": "object",
"id": "https://[URL_NAME]/forms/{id}/...#",
"properties": {
"title" : { "type": "string" },
"date" : { "type": "string" },
"content" : { "type": "string" },
"date_start": { "type": "string" },
"date_end" : { "type": "string" },
"status" : {
"type" : "string",
"enum" : ["1", "2", "3", "4", "5"]
}
},
required [
"title",
"date",
"content",
"date_start",
"date_end",
"status"
]
}

See if you can notice the error is this schema. Don't copy and paste it. I change some format to obsfucate the real data naming, but this schema error is still up there

Just wasted my 30 minutes staring at this

Comments
  • 0
    looks like:

    "enum" : ["1", "2", "3", "4", "5"]
    }
    },

    should be:

    "enum" : ["1", "2", "3", "4", "5"]
    },
  • 10
    "required":
  • 1
    URL invalid. *JK*
  • 0
    @kunashe
    Eh. It's actually gonna be one more errors if you do that

    @stop
    Noice

    @Huuugo
    😂 God please kill me
  • 0
    @greenrobo yip! @stop showed me the way.
  • 0
    @kunashe i only wrote too much json.
  • 0
    @stop I wonder if that is a bad or good thing 🤔
  • 0
    What editor are you using? Most editors would highlight wrong syntax. Atom does it
  • 0
    @Positive07 atom does that? I should try it. I do JSON schema on notepad++. Because.. well, I rarely do them
  • 0
    Oh I see, Notepad++ is good, fast and lightweight but it lacks many features.

    Atom is great and if it doesn't fit your needs there will most likely be a plugin to fix that.

    It's way heavier than Npp but that isn't a problem nowadays, and it is slower, but it is getting faster, specially with the latest release
Add Comment