WindmillWWindmill
Powered by
inakiabtI
Windmill•3y ago•
5 replies
inakiabt

Nested JSON schema required fields

Hi, I have the following schema where the goal is to make "name" and "id" required within "Persona" (also set the order of the fields).

For some reason it doesn't work.

Am I missing something or is it an issue?
Thanks.

{
    "properties": {
        "Persona": {
            "type": "object",
            "description": "",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "",
                    "default": ""
                },
                "id": {
                    "type": "number",
                    "description": ""
                },
            },
                        "order": ["name", "id"],
            "required": [
                "name",
                "id"
            ]
        }
    },
    "required": [
        "Persona"
    ],
    "type": "object",
    "order": [
        "Persona"
    ]
}
{
    "properties": {
        "Persona": {
            "type": "object",
            "description": "",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "",
                    "default": ""
                },
                "id": {
                    "type": "number",
                    "description": ""
                },
            },
                        "order": ["name", "id"],
            "required": [
                "name",
                "id"
            ]
        }
    },
    "required": [
        "Persona"
    ],
    "type": "object",
    "order": [
        "Persona"
    ]
}
WindmillJoin
3,362Members
Resources
Recent Announcements

Similar Threads

Was this page helpful?
Recent Announcements
henri-c

Weekly kenote to tell you about our latest updates https://discord.com/channels/930051556043276338/1278977038430240813 https://youtube.com/live/2dGd9TdT8xs?feature=share

henri-c · 4d ago

Pyra

### HTTP tracing (EE) Capture HTTP requests made by job scripts as observability spans Features: - View HTTP request traces (method, URL, status, timing) in the job details UI - Auto-instrumentation for Native TypeScript, MITM proxy for other languages - Integrates with external OpenTelemetry collectors changelog: https://www.windmill.dev/changelog/http-tracing docs: https://www.windmill.dev/docs/advanced/instance_settings#http-tracing Additionally jobs memory metrics are now fully OSS!

Pyra · 2w ago

henri-c

First keynote of the year here https://discord.com/channels/930051556043276338/1278977038430240813 🙂

henri-c · 4w ago

Similar Threads

Creating flow input schema from nested JSON
Lucas HicksLLucas Hicks / help
17mo ago
App: Required input fields
tl_jacobTtl_jacob / help
5mo ago
App JSON Schema
fooosieeeFfooosieee / help
2mo ago
Unable to Reset Form for Object-Type Fields in JSON Schema-Based Form
DeepakDDeepak / help
13mo ago