Is your feature request related to a problem

Coming from this issue: tiangolo/fastapi#817

The docs have some sections with functions using *, in the parameters.

It is explained here: https://fastapi.tiangolo.com/tutorial/path-params-numeric-validations/#order-the-parameters-as-you-need-tricks

But in other sections like: https://fastapi.tiangolo.com/tutor

reproduce:

• try a schema without "properties" keyword in the playground
• and a initial-formData of type object ...

=> make sure the formData is a string to have it fixed

Warning: Failed prop type: Invalid prop `value` supplied to `TextWidget`.
    in TextWidget
    in Unknown (created by StringField)
    in StringField (created by SchemaField)
    in div (created by WrapI

This is an issue with the documentation.

**The version of Ajv you are using

The tool generates code that causes PMD UnnecessaryModifier warnings for generated enums .
(https://pmd.github.io/latest/pmd_rules_java_codestyle.html#unnecessarymodifier)
It might make sense to change the autogenerated code not to have

    private SomeEnum(String value) {
        this.value = value;
    }

but

SomeEnum(String value) {
    this.value = value;
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$ref": "#/definitions/foo",
  "definitions": {
    "foo": {
      "type": "object",
      "properties": {
        "bar": {
          "$ref": "bar.json#"
        },
      },
      "required": [
        "bar"
      ],
    },
    "title": "foo"
  }
}

Running quicktype CLI with this Schema produces

Error

Feature Request

It would be great to include API documentation. The Usage docs are great as a walkthrough, but when you want to go fast ("what is the name for the Field parameter for a constant value?"), API docs provide a faster answer.

Another use case: I want to inspect the __fields__ on a model, and had to read the code to get the attribute name I was looking for.

API docs would

Expected behaviour

If a property that is defined as required in the schema, is absent from the form (and model), the model should fail validation

Actual behaviour

The model passes validation

Gist/Plunker/Demo

This demo modifies the [simple example](http://schemaform.io/examples/boots

It doesn't seem clear in the spec that a schema evaluates to true if all its keywords also evaluate to true. i.e. an allOf behaviour.

The current README file mentions options such as throwError and nestedErrors. Others, unfortunately, can be learned only by looking at the source code.

Please add the options and their descriptions to the README.

The others I found:

• propertyName
• base
• skipAttributes
• allowUnknownAttributes
• rewrite
• disableFormat

https://github.com/bcherny/json-schema-to-typescript/blob/d898361ff973d3746ea695f1efce75c975061c6f/src/utils.ts#L164

The member of type name is restricted to only english letters (and some symbol)
Typescript now allows unicode characters (doc link)

So, modify this function to a

The title might seem a bit vague but I don't know how to describe it any better tbh :-)

Anyway this is what happened: I got some 500 responses from the schema registry and all I could see in the logs was :

[2020-04-02 16:03:35,048] INFO 100.96.14.58 - - [02/Apr/2020:16:03:34 +0000] "PUT /config/some-topic-value HTTP/1.1" 500 69  502 (io.confluent.rest-utils.requests)

The logs di

i found https://stackoverflow.com/a/38781027/2602592 extremely helpful as a reference for understanding the different approaches to schemas depending on field values.

it covers dependencies, anyOf (Implication) and if-then-else

Would be a wonderful addition, though in the answer spans till v7.

I want a resource with an array of a sub-resource, and everything properly checked for validity.

As a preamble, I found two ways of declaring a sub-resource and I fail to see the difference between them. First approach:

Fields: schema.Fields{
    "sub": {
        Schema: &subresource
    },
}

Second approach:

Fields: schema.Fields{
    "sub": {
        Valida

When I run the sample from https://github.com/marshmallow-code/apispec/blob/dev/docs/quickstart.rst

the expected output

# {'components': {'parameters': {},
#                 'responses': {},
#                 'schemas': {'Gist': {'properties': {'id': {'format': 'int64',
#                                                            'type': 'integer'},
#                                

Currently the example value can have a different data structure that is defined in the schema and the swagger-cli validate doesn't rise an error.

example:
    foo:
        bar: a
        baz: b
type: object
properties:
    foo:
        type: integer
        format: int32
        default: 0

I think it would be very useful if the example value would be validated against

Due to this:
https://github.com/facebook/jest/pull/9841/files
and this:
https://github.com/sindresorhus/conf/blob/410cc144141f1467cc91fe4b16f6b7f42a8afac8/index.js#L21-L23
=>

console.warn
    `require.cache` modification is not permitted

(output'ed many times in the console when unit-testing, with full stacktrace, so quite disruptive, albeit non-fatal unless unit-tests check for C

"Require calls will work only in Node.js, and will cause errors for anyone trying to use the ruleset in the browser. If your ruleset is definitely going to only be used in the context of NodeJS then using them is ok, but if you are distributing your rulesets to the public we recommend avoiding the use of require() to increase portability."

I have a extensions.js file that has functions I reuse

This is very minor, but I think the colon should not be there here https://github.com/brutusin/json-forms/blob/master/src/js/brutusin-json-forms.js#L1034

User can choose to add a colon in his decorator.

According to the Mongoose arrays documentation, an array default value is possible.
But in schm, when array of schema is validatate, the default value is always an empty array.

Inspired example from Mongoose

const ToySchema = schm({ name: String });
const ToyBoxSchema = schm({
  toys: {
    type: [ToySchema],
    defaul

I believe the accept-merge method should be wrapped in a call to maybe-with-title, same as the accept-spec implementation for clojure.spec.alpha/keys

https://github.com/metosin/spec-tools/blob/d3456858d49ccdb52823dddd08a865a811dfcb7b/src/spec_tools/json_schema.cljc#L208

The latest version needs to reflect:

• No more use of AutoValue
• Ability to check which fields are "set"
• Updated usage pattern for TypeAdapters
• Other minor changes