Validation error on nullable parameters with a format about openapi4j HOT 11 CLOSED

Welcome and thank you for the report.
The issue is about the format validator which did not detect the null value.

Can you confirm the fix in the latest snapshot? It should be already available.

from openapi4j.

@llfbandit Thank you for the quick response.
Where is 0.6-SNAPSHOT being published? I can't seem to find it in the maven repo.

Also, is there an estimate on when 0.6 will be released?

from openapi4j.

You have to add https://oss.sonatype.org/content/repositories/snapshots before accessing snapshot versions.

I'm waiting for #28 confirmation before bumping to 0.7 so a couple of days I would say.

from openapi4j.

You have to add https://oss.sonatype.org/content/repositories/snapshots before accessing snapshot versions.

I'm waiting for #28 confirmation before bumping to 0.7 so a couple of days I would say.

The above test throws a NullPointerException with 0.6-SNAPSHOT. It seems to be coming from ReferenceValidator. More specifically, schemaParentNode.get(ABS_REF_FIELD) is null. The schema parent node contains a normal $ref instead of an absolute ref. Aren't both valid in that context?

from openapi4j.

This is due to the usage of toNode which serialize the content with constraints to reflect the definition of OAI. The field ABS_REF_FIELD is not exported in this case. This why you get the RuntimeException.

If you really use the toolset like with the reproducer you'll need to use TreeUtil.toJsonNode to keep the info.

To let me know, what kind of usage do you have? For this kind of validation process, the operation validator is dedicated to make the glue code between parser and schema validation modules.

from openapi4j.

I updated the code to JsonNode jsonNode = TreeUtil.toJsonNode(schema); but I am still getting the same NullPointerException. I updated the test case in the original post accordingly so it can be reproduced.

from openapi4j.

To let me know, what kind of usage do you have? For this kind of validation process, the operation validator is dedicated to make the glue code between parser and schema validation modules.

We are using the schema validator to validate input and output payloads against the schemas defined in the OpenAPI definition of the REST API.

from openapi4j.

0.6 introduced this bug. Sorry for that.
This invalidates 0.6 as a release for now. You can follow up this subsequent fix to the dedicated issue #28.

from openapi4j.

0.6 introduced this bug. Sorry for that.
This invalidates 0.6 as a release for now. You can follow up this subsequent fix to the dedicated issue #28.

Ok thank you I will keep an eye on #28

from openapi4j.

Can you validate this issue ? We're pretty close to conclude on the other side. Thank you.

from openapi4j.

Validated. Seems to be fixed. Thank you very much for the quick turnaround.

from openapi4j.