-
I'm getting an `OBJECT_MISSING_REQUIRED_PROPERTY` error on a sample for "api-version" despite the fact it's there in the [sample](https://github.com/Azure/azure-rest-api-specs/blob/db344f8a6cbbf157414…
-
Description of bug:
Currently when I load my form I have a reactive state with an array which I am then applying rules to. Using the $each and helpers.foreach functons I am able to see errors. Fantas…
-
```
public class GuidNotEmpty : Validation
{
public GuidNotEmpty(string property) : base(property)
{
}
public override void Init(dynamic entity)
{
base.Init(entity as object);
if (…
-
ATM it is
```
Usage: bids-validator [options]
```
whenever BIDS-app interface, as described in new exec spec (bep027) https://bids-standard.github.io/execution-spec/inputs.html#backwards-com…
-
**Introduction:**
The current SDMX-JSON data message specification requires that the `data.structure` object reference the Data Structure Definition (DSD) through a link to the Data Provision Agree…
-
Is it possible to have the validation restrict properties? I not only want to validate properties I know about but also make sure no properties get in that I don't already know about.
-
The spec allows `"type": []`, but in the validation vocabuary there is a 'minItems: 1' for the "type" property. This seems inconsistent.
For details see this issue I filed earlier with the test…
aha79 updated
2 months ago
-
By Charles Munat:
Rather than provide an error object with message and property name, why not return as the error object the property's type info itself, merging in a message and the type of failure?…
-
Potentially related to https://github.com/microsoft/vscode-json-languageservice/issues/86
## Use Case
I'm currently working with a schema that has a common definition "oneOf"ed with other proper…
-
### Bug type
Component
### Component name
MudFormComponent
### What happened?
Error and ErrorText parameters are reset by internal component validation. Externally set Error and ErrorText only wo…