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 could be a good idea to add a named parameter to fields in order to restrict them to a specific address family.
Of course, I'm not talking about an address family restriction on a database level but on a model level. In this way a model could include only IPv4 (or IPv6) address fields.
By default, a field could accept both IPv6 and IPv4 addresses (or networks) or if given a named parameter (family for instance), it will validate the value passed to it, checking it it from the right address family.
I can work on a PR if this issue is proposal is legit.
The text was updated successfully, but these errors were encountered:
It could be a good idea to add a named parameter to fields in order to restrict them to a specific address family.
Of course, I'm not talking about an address family restriction on a database level but on a model level. In this way a model could include only IPv4 (or IPv6) address fields.
By default, a field could accept both IPv6 and IPv4 addresses (or networks) or if given a named parameter (
family
for instance), it will validate the value passed to it, checking it it from the right address family.I can work on a PR if this issue is proposal is legit.
The text was updated successfully, but these errors were encountered: