Skip to content

Conversation

@uhlikfil
Copy link

@uhlikfil uhlikfil commented Jun 1, 2023

Allow users to specify not found value to distinguish between incorrect expression and actual None value in the data.

Resolves #186

@uhlikfil uhlikfil changed the title [#186] options: add default not found value option [#186] options: add custom not found value option Jun 2, 2023
@uhlikfil
Copy link
Author

Can someone take a look please? We'd really like this feature to be available in JMESPath.

@uhlikfil
Copy link
Author

uhlikfil commented Aug 5, 2023

@jamesls Is there any chance this could get noticed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Custom "None" value when search fails

1 participant