Skip to content

JSON Schema for the Specification #11

Description

@matthewhudson

I've added some JSON Schemas describing the block definition, inputs, and outputs.

I used the file extension ".schema.json" because, as far I can tell, there is no standard file extension (reference).

All three schemas will require updates to accomodate nested objects inside inputs/outputs. Not sure if JSON Schema uses 'items', or 'additionalItems', or something else altogether. Please advise.

Once we have these schema ironed out we'll be able to put together a validator for others to test against.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions