Closed mabar closed 1 year ago
Nah, better solve it by rules like BigIntRule with brick/math under the hood
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
It may be useful to support pseudo-tpyes like
numeric-string
, so constructions likestring&&int<acceptNumericString>
are not needed.e.g.
IntRule
can replacecastNumericString=true/false
option withnumericString=require/optionally/never
.TODO - list all rules which should be modified
Reasoning: https://github.com/orisai/object-mapper/issues/10#issuecomment-888481041