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
Frontend has handed me the following error stemming from our new Javers implementation:
Exception in thread "Thread-143" java.lang.IllegalArgumentException: argument should not be null
at org.javers.common.validation.Validate.argumentsAreNotNull(Validate.java:33)
at org.javers.core.JaversCore.commit(JaversCore.java:80)
at org.javers.core.JaversCore.commit(JaversCore.java:69)
The problem is that this error does not happen in the backend tests that I have, and just from the error message, I can't say which of the possible arguments is null.
It would be great if the error message could specify which of the arguments was null.
The text was updated successfully, but these errors were encountered:
Frontend has handed me the following error stemming from our new Javers implementation:
The problem is that this error does not happen in the backend tests that I have, and just from the error message, I can't say which of the possible arguments is null.
It would be great if the error message could specify which of the arguments was null.
The text was updated successfully, but these errors were encountered: