Skip to content
This repository has been archived by the owner on Apr 24, 2022. It is now read-only.

Avoid sending values of 0 where there is no data #70

Open
nightsh opened this issue Dec 1, 2017 · 3 comments
Open

Avoid sending values of 0 where there is no data #70

nightsh opened this issue Dec 1, 2017 · 3 comments

Comments

@nightsh
Copy link
Member

nightsh commented Dec 1, 2017

image

If there is no data for a value, simply send null or nothing. We have ways of treating them in frontend, but 0 is a value and we will display as it is.

@chutko
Copy link

chutko commented Dec 1, 2017

i think its not about what value is sent, rather than what we do with it.
if there is zero value we can display different content, for example message "no data"

@nightsh
Copy link
Member Author

nightsh commented Dec 1, 2017

@zufanka does it make sense, or we could actually have a legit 0 value anywhere? If so, we can also format values of 0 as something like "n/a" or "y u no data" or whatever.

@zufanka
Copy link
Member

zufanka commented Dec 1, 2017

I don't think there are any legit tenders for 0 money :) Or 0 contracts
I would go for "no data" or "data missing" because "NA" means "not applicable" while it is quite applicable, just missing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants