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
Currently the schema excludes the possibility of optional fields being present with null values. It seems like the expected behaviour is that where data is missing, the fields must always be excluded.
I just want to check this is intentional.
(I could imagine, for example, a system which outputs data where all fields are present, and the missing ones are simply left blank. At the moment that wouldn't validate - but there's an easy change to the schema to ensure it would.)
Either way, if this is intended behaviour, we should make sure it's documented, so that the situation I just imagined never comes to pass!
The text was updated successfully, but these errors were encountered:
Currently the schema excludes the possibility of optional fields being present with null values. It seems like the expected behaviour is that where data is missing, the fields must always be excluded.
I just want to check this is intentional.
(I could imagine, for example, a system which outputs data where all fields are present, and the missing ones are simply left blank. At the moment that wouldn't validate - but there's an easy change to the schema to ensure it would.)
Either way, if this is intended behaviour, we should make sure it's documented, so that the situation I just imagined never comes to pass!
The text was updated successfully, but these errors were encountered: