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
Filter fields with null values in exported dashboard model #54126
Comments
We use |
This feels like one case where it'd be OK to break the "no nulls in JSON" rule. That's simply because, if browsers stringify That said, i am concerned about how we would account for JS having both negative and positive infinity - |
This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions! |
This issue has been automatically closed because it has not had any further activity in the last 30 days. Thank you for your contributions! |
One background goal with schematization is that we disallow any field, in any schematized object, from containing an explicit
null
value. Much ink could be spilled over this, but it is essentially because it reduces ambiguity: by banning nulls universally, we make it so that no one authoring a schema ever has to answer the question, "if a field exists with valuenull
, is that meaningfully different from that field being absent?"#41385 helped a lot with this by purging nulls from dashboard JSON that's sent for save. But we're still producing nulls on export, which is why PRs like #54124 end up happening - to fix something that was exported (and avoided the test that should have caught it that i only just fixed in #53797 😱).
We need to go the additional step of also stripping nulls from exported dashboard JSON.
cc @joshhunt @ryantxu
The text was updated successfully, but these errors were encountered: