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
Most use of @Value.Check doesn't actually do normalization, it just does checking. This should be fairly easy to support even when the constructors are directly exposed.
This might also be an indication that the ad-hoc normalization deserves its own annotation rather than reusing @Value.Check (which is quite non-obvious itself).
The text was updated successfully, but these errors were encountered:
Thank you for creating a request. If I understand correctly, the suggestion is to allow calling precondition checking methods from within constructors (at the end of construction). I guess we can frame it as when we don't do normalization and have a check method we call it at the end of construction for of="new" style.
I understand and somewhat share your thinking around separate annotation/feature for normalization, but it's, probably, not worth it at the moment wrt compatibility and cost-to-benefit ratio
Most use of @Value.Check doesn't actually do normalization, it just does checking. This should be fairly easy to support even when the constructors are directly exposed.
This might also be an indication that the ad-hoc normalization deserves its own annotation rather than reusing @Value.Check (which is quite non-obvious itself).
The text was updated successfully, but these errors were encountered: