code completion breaks when anyOf defines required properties.

[manoj-pillay-10gen]

#204 describes an issue with anyOf (and oneOf) error messaging. However, one way to solve this is to provide a schema-specific error message using the custom JSON property errorMessage as illustrated in this example.

However, the use of the required property (or the dependencies property) on anyOf subschemas will prevent monaco from surfacing it as a valid suggestion. In my example above, p1.shape can be fulfilled by both rectangle and square. However, the only autocomplete option that gets offered is rectangle

The reason this occurs is because the square subschema defines a required field side that is only available within that schema. It essentially ends up making square a hidden option for p1.shape critically breaking the expected completion.

PS: If side were to be removed from the required array in L62 of the example, completions start working as expected.

[jeremyfiel]

if you remove type: string it surfaces the error. This is a bug in the monaco implementation.

This one has got it right. https://json-schema.hyperjump.io

[manoj-pillay-10gen]

The problem highlighted in this github issue is that code completion does not work as expected and only offers one among many choices that may be available for the property defined using the oneOf/anyOf construct. I wonder if the issue is more with vscode-json-languageservice treatment of oneOf/anyOf rather than it being with monaco itself.