Is there a way to disable/restrict string mutations for specific fields during generative tests

[prateekkarmakar]

Consider If the API spec defines properties as strings without restrictions, generative tests can result in Boolean or integer values being accepted as strings. Setting patterns with examples isn't foolproof. Negative test scenarios that mutate a string to a Boolean or integer will fail as the service will consider them valid once de-serialized by Jackson Json parsing library.

Is there a way to tell Specmatic not to generate a negative test that mutates a specific string or integer property in the Open API spec.
or
Is there a way to disable string mutation altogether in Specmatic config.

As mentioned adding pattens may not be feasible for all scenarios and cant put everything in ENUMs