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
the existing API isn’t very clear about whether the passed keys are explicitly allowed to appear, or explicitly prohibited from appearing. we should give it an argument label, like whitelisting:
The text was updated successfully, but these errors were encountered:
after some real world use of this API, it's also not always clear if the whitelisted keys are eagerly or lazily removed… current behavior is the client is still able to access these keys from within the body of the closure, which seems at odds with the spelling json.lint(_:)
also unclear is what happens if the whitelist includes keys that are not present in the decoding container. currently the library ignores them.
need to evaluate source breakage, as this API is already in use by a few downstream packages
the existing API isn’t very clear about whether the passed keys are explicitly allowed to appear, or explicitly prohibited from appearing. we should give it an argument label, like
whitelisting:
The text was updated successfully, but these errors were encountered: