Strange pattern property is being added

[dhoffer]

We are noticing some of the object properties have a pattern field that we don't know where it came from. I looked for a quarkus or mp property to disable but did not find one. How can we remove these?

"marking": {
"description": "Marking of the data",
"maxLength": 128,
"minLength": 1,
"pattern": "\S",
"type": "string",
"example": "U"
},

[MikeEdgar]

That pattern is set when the property has a @NotBlank constraint. It indicates the value must contain a non-whitespace character.

[MikeEdgar]

There is not. Are you thinking it is not correct for some reason or you'd just prefer not to have it?

[dhoffer]

Our app testers don't like it so filled a bug report.

Some required string fields display a "matches \S" badge that is not going to be helpful to end users. I'm guessing this is coming from the schema pattern attribute that was added. I suggest removing that everywhere.

We do have an OASFilter so I suppose I could null it out there. But yeah we are not fans of the framework auto adding stuff that we did not ask for/enable.

[MikeEdgar]

I can understand that it's not end-user friendly for those not familiar with regex. It's similar to auto-adding maxLength or minLength values based on the presence of a @Size annotation.

It can be disabled with the following option, but that affects all constraint annotations and not just @NotBlank.

mp.openapi.scan.beanvalidation=false

See also https://download.eclipse.org/microprofile/microprofile-open-api-4.0.2/microprofile-openapi-spec-4.0.2.html#_jakarta_bean_validation_annotations

[dhoffer]

Okay, I'm checking to see if we can get leave it alone.

[dhoffer]

We ended up using the filter to set the pattern to null. We don't want these new OpenAPI features unless we enable them, as it would have caused confusion for our OpenAPI users.