Null value causes incorrect error "property not found"

[rhtenhove]

Using today's dasel:2-alpine image (dasel version v2.6.0)

I use dasel to parse settings from the GitLab Project API. Today, for the first time, I received an error that a property was not found in the API output. Upon further inspection, the value for that property turned out to be null instead of missing.

I am not sure if this was changed by GitLab by returning null if the setting is unset, instead of the default boolean. Either way, I would expect dasel to return the value, null, instead of failing with the incorrect feedback that the key is missing.

How to reproduce:

$ echo '{"iamnull": null}' | dasel -r json "iamnull"
Error: could not access map index: property not found: iamnull

[TomWright]

Hey @rhtenhove,

This looks like a duplicate of #346.

I'm going to close this in favour of the other issue.