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
I am trying to create a JSON Schema converter and there are some limitations that I think could be addressed in the system packagees
For example in the In net package support
is_IPv6() to validate ipv6 only which returns False for an ipv4 address
In datetime have functions to validate RFC 3339 dates and times and durations and also another for ISO 8601, having single pattern validation doesnt work for JSON schema. Where timezone is optional and where microseconds are optional.
For example all of these are valid accoring to JSON schema, for now I use regex to valiate but with regex I can't validate leap years Feb 29 etc ...
2024-03-20T15:30:00Z
2024-03-20T15:30:00.123Z
2024-03-20T15:30:00+01:00
2024-03-20T15:30:00.123+01:00
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am trying to create a JSON Schema converter and there are some limitations that I think could be addressed in the system packagees
For example in the In net package support
is_IPv6() to validate ipv6 only which returns False for an ipv4 address
In datetime have functions to validate RFC 3339 dates and times and durations and also another for ISO 8601, having single pattern validation doesnt work for JSON schema. Where timezone is optional and where microseconds are optional.
For example all of these are valid accoring to JSON schema, for now I use regex to valiate but with regex I can't validate leap years Feb 29 etc ...
2024-03-20T15:30:00Z
2024-03-20T15:30:00.123Z
2024-03-20T15:30:00+01:00
2024-03-20T15:30:00.123+01:00
Beta Was this translation helpful? Give feedback.
All reactions