Peter Urbak

It would be nice if all public functions had a `@spec` type specification so it becomes more obvious from the documentation what types can be given to a function without...

Investigate supporting the 'default' keyword

2

Investigate whether it makes sense to support the 'default' keyword, see 7.3 in the [validation spec](http://json-schema.org/latest/json-schema-validation.html#rfc.section.7.3).

Support constants, i.e. enums with 1 value.

1

Also while looking at enums: remove the `"type": "string"` constraint, if possible.

See http://json-schema.org/latest/json-schema-validation.html#format For example, if we have the node ``` "datum": { "required: ["createdDate"] "properties": { "createdDate": { "type": "string", "format": "date-time" } } } ``` we want it to...

Investigate whether there is a reasonable type+parser+decoder that can be generated from the generic types: ``` { "type": "object" } ``` and ``` { "type": "array" } ``` i.e. maybe...

Currently, we don't recognise subschemas which may contain both a `"definitions"` property and a `"type"` property. The current assumption is that all definitions are contained in the `"definitions"` property of...

Hi I think I may have found a small bug: if I have an input form and I tab through the input fields, then when I get to the `elm-select-two`...