Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling missing values and no fallback #3662

Closed
clausjensen opened this issue Jun 6, 2018 · 1 comment
Closed

Handling missing values and no fallback #3662

clausjensen opened this issue Jun 6, 2018 · 1 comment

Comments

@clausjensen
Copy link
Contributor

clausjensen commented Jun 6, 2018

When there is "no value" we want to fall back to something else - but how can you indicate that a value is "intentionally empty" ie "no value" actually means "no value, please don't fallback"?

child of #3661

@clausjensen clausjensen transferred this issue from another repository Nov 15, 2018
@zpqrtbnk
Copy link
Contributor

It is partially done already. I think each property value converter can implement HasValue so that... you can ask the converter whether a value is actually a value or not. So a converter may decide to report a null value as a valid value. Basically... now the burden is on the converters. If we're OK with this, then we prob only need to verify and close.

@ghost ghost removed the state/maturing label Jan 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants