Future proof JSON schema -

-

is possible force known objects ("enemy" , "friend") defined while other objects allowed?

i've added last object {"type": "object"} display intended behaviour - in reality last object overrule 2 defined objects ("enemy" , "friend") causing kind of object valid schema. if remove last object, allow 2 objects nothing else.

json schema (using array faster testing):

{   "type": "array",   "items": {     "anyof": [       {"$ref": "#/definitions/friend"},       {"$ref": "#/definitions/enemy"},       {"$ref": "#/definitions/future"}     ]   },   "definitions": {      "friend": {       "type": "object",       "properties": {         "time": {"type": "string"},         "value": {"type": "number", "minimum": 100}       },       "required": ["time", "value"],       "additionalproperties": false     },      "enemy": {       "type": "object",       "properties": {         "enemy": {"type": "string"},         "color": {"type": "number"}       },       "required": ["enemy", "color"],       "additionalproperties": false     },      "future": {       "type": "object",       "properties": {         "time": {"type": "string"}       }, "required": ["time"],       "additionalproperties": true     }    } }

example json (top 3 should ok, last 3 should not ok):

[   {"time": "123", "value": 100}, <- should valid   {"time": "1212", "value": 150}, <- should valid   {"enemy": "bla", "color": 123}, <- should valid   {"time": "1212", "value": 50}, <- should invalid bcoz of "future"   {"enemy": "bla", "color": "123"}, <- shouldn't valid bcoz of "enemy" schema   {"somethinginfuture": 123, "somefutprop": "ok"} <- should valid ]

it's not clear want want use combination of dependencies , minproperties here. 2 forms of keyword used here: property dependency , schema dependency. want @ least 1 property defined, hence minproperties. can (note factorized common schema color; may, or may not, want):

{     "type": "object",     "minproperties": 1,     "additionalproperties": {         "type": "string" // properties not explicitly defined strings     },     "properties": {         "color": { "type": "number" }     },     "dependencies": {         "enemy": "color", // property dependency         "friend": { // schema dependency             "properties": { "color": { "minimum": 50 } },             "required": [ "color" ]         }     } }

note schema still allows "enemy" , "friend" @ same time (so original schema). better, sample jsons want deem valid , invalid should provided.


Comments

Post a Comment

Popular posts from this blog

python - TypeError: start must be a integer -

-
i trying draw 5 turtles, getting typeerror on line 25. here code: import turtle wn = turtle.screen() redrose = turtle.turtle() color = input("what background color be?") fillcolor_f = input("what color of rose be?") redrose.hideturtle() redrose.speed(30) redrose.penup() redrose.left(180) redrose.forward(175) redrose.right(90) redrose.forward(30) redrose.right(90) redrose.pendown() def drawrose(red): redrose.color("pink") redrose.fillcolor(fillcolor_f) redrose.fill(true) in range(red): redrose.forward(i) redrose.right(49) in range(5): drawrose(redrose) redrose.penup() redrose.forward(350) redrose.right(144) redrose.pendown() redrose.fill(false) drawrose(50) wn.bgcolor(color) i trying draw 5 roses, produces errors. doing in interactivepython.org. you recursively calling drawrose wrong parameter. on line 23 ( for in range(red): ) expect red integer...
Read more

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

-
i have following code almost works properly; private void cbstatus_drawitem(object sender, listboxdrawitemeventargs e) { string item = e.item string; if (item != null) { switch (item) { case "1": e.appearance.forecolor = color.green; e.appearance.backcolor = color.green; break; case "2": e.appearance.forecolor = color.orange; e.appearance.backcolor = color.orange; break; case "3": e.appearance.forecolor = color.red; e.appearance.backcolor = color.red; break; } } } when dropdown shown, items forecolor correct, backcolor remains whatever backcolor of theme is; i.e. if i've got set dark theme, backcolor dark, cells in gridview, rather being green/orange/red. i've tried setting e.appearance.options.usebackcolor trying set e....
Read more

django - Creating multiple model instances in DRF3 -

-
1) create multiple model instances 1 api call, asked here: how create multiple model instances django rest framework? tried solution named in link, no success. i trying upload multiple files in 1 api call. result: files uploaded (only once overwrote perform_create) 1 instance created (if send 2 files, latter created instance). my code: class fileuploadserializer(serializers.modelserializer): def __init__(self, *args, **kwargs): many = kwargs.pop('many', true) super(fileuploadserializer, self).__init__(many=many, *args, **kwargs) class meta: model = fileupload read_only_fields = ('created', 'datafile', 'owner') class fileuploadviewset(viewsets.modelviewset): queryset = fileupload.objects.all() serializer_class = fileuploadserializer parser_classes = (multipartparser, formparser, ) def perform_create(self, serializer): file_list = self.request.data.getlist('file') ...
Read more