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
Please consider adding support for prohibited keys in maps. This is similar to use = prohibited on attributes in xsd (see https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/ms256143(v=vs.100) This is useful in validation scenarios when we want to accept open maps but explicitly specify certain keys this map should not contain (e.g. :error). I am aware of the built-in :fn schema, but IMHO adding the support to the built-in :map (similar to {:closed true}) would be cleaner.
The text was updated successfully, but these errors were encountered:
Please consider adding support for prohibited keys in maps. This is similar to
use = prohibited
on attributes in xsd (see https://learn.microsoft.com/en-us/previous-versions/dotnet/netframework-4.0/ms256143(v=vs.100) This is useful in validation scenarios when we want to accept open maps but explicitly specify certain keys this map should not contain (e.g.:error
). I am aware of the built-in:fn
schema, but IMHO adding the support to the built-in:map
(similar to{:closed true}
) would be cleaner.The text was updated successfully, but these errors were encountered: