Add new Json schema properties

[imIfOu]

feat: add "default" value properties
feat: add "required" properties
feat: add resolve metadata
conf: add more rules in gitignore

[imIfOu]

Hello,

If you want more details on the use of this new properties, you can check my module.

Best regards,

[CarstenWickner]

Hi @FlorianDidier,

I like the idea of properly supporting the "required" and "default" attributes.
I'm not a fan of the generic "metaData" though since this kind of generic addition of attributes to a field or method is already supported via SchemaGeneratorConfigPart.withInstanceAttributeOverride().

E.g. in your module-addon project, you'd only have to:

• replace the .withMetadata(this::resolveMetadata) call with .withInstanceAttributeOverride(this::resolveMetadata) and
• change the resolveMetadata() method to this:

protected void resolveMetadata(ObjectNode jsonSchemaAttributesNode, MemberScope<?, ?> member) {
    this.getAnnotationFromFieldOrGetter(member, JsonSchema.class)
            .map(JsonSchema::metadata)
            .ifPresent(metaData -> Stream.of(metaData)
                    .filter(data -> !data.key().isEmpty())
                    .filter(data -> !data.value().isEmpty())
                    .forEach(data -> jsonSchemaAttributesNode.put(data.key(), data.value())));
}

That way you could theoretically also add the "required" and "default" attributes yourself already, but since those are standard attributes I like your proposed solution of supporting them specifically.

To summarise: after removing the changes related to the meta-data handling and cleaning-up some of the unnecessary style/import changes, I'm happy to merge this PR.

Thank you very much for your input. 👍

[CarstenWickner]

There is no Gradle in this project, but I like the idea of catering for more IDEs out-of-the-box.

[CarstenWickner]

We seem to have different configurations for the order of imports. 😉
I'd rather be consistent throughout the project and not include those order changes here.

[CarstenWickner]

"format" as the variable name is a bit confusing to me here. it is the "defaultValue".

[CarstenWickner]

I like the general idea. I'll do the clean-ups myself and share the new PR (against the "master" branch) with you then.

[CarstenWickner]

@FlorianDidier the support for the new "required" and "default" properties (together with the general support of the "pattern" property) have been released now as v3.2.0.

As per my previous comment, I removed the proposed addition of a "metaData" map, as the existing SchemaGeneratorConfigPart.withInstanceAttributeOverride() does already support that (and more).

Thank you for your contribution!