You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems, that the ByteBuddy imposterizer is too strict when mocking classes. We have the following situation:
a scala case class has a field annotated with @JsonIgnore
the scala compiler adds this annotation to the parameter corresponding with the field in the scala generated copy method
ByteBuddy type validation fails, because @JsonIngore is not marked as being valid for parameters
I believe that JMock should not validate the generated class as the validation is too strict and if the source class is not strictly valid according to ByteBuddy, it's impossible to mock such a class at all.
What are your thoughts?
I'll submit a PR shortly
The text was updated successfully, but these errors were encountered:
It seems, that the ByteBuddy imposterizer is too strict when mocking classes. We have the following situation:
@JsonIgnore
copy
method@JsonIngore
is not marked as being valid for parametersI believe that JMock should not validate the generated class as the validation is too strict and if the source class is not strictly valid according to ByteBuddy, it's impossible to mock such a class at all.
What are your thoughts?
I'll submit a PR shortly
The text was updated successfully, but these errors were encountered: