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
Looks like you recently added a check for JSON so that if the type is null, you throw an error. Surely the same check would apply to the YAML and allow you to avoid nullable returns which push error handling out of library into consumer code.
The text was updated successfully, but these errors were encountered:
using defaults, enable the same exception as was used for JSON, to be used for YAML
move the check for JSON so that undefined types result in error case always (rather than defaulting to JSON decode with 'Unknown' as the outcome from non-js/json file extension
Fixesshaggy8871#1
using defaults, enable the same exception as was used for JSON, to be used for YAML
move the check for JSON so that undefined types result in error case always (rather than defaulting to JSON decode with 'Unknown' as the outcome from non-js/json file extension
Fixesshaggy8871#1
Looks like you recently added a check for JSON so that if the type is null, you throw an error. Surely the same check would apply to the YAML and allow you to avoid nullable returns which push error handling out of library into consumer code.
The text was updated successfully, but these errors were encountered: