You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry, I found another small bug. I accidentally set nil, instead of "0", to badgeValue, and the badge still shows even after shouldHideBadgeAtZero is set as YES.
The expected behaviour should be that the badge don't show when nil value, since nil is somehow the same than 0. What do you think?
The text was updated successfully, but these errors were encountered:
That was just wrong... sorry.
I consider that if the badgeValue is set to nil or with an empty string it should removed.
Zero is a special case, because zero could be considered as an info to the user. Whereas an empty string and nil definitely not.
Thanks for your help.
Sorry, I found another small bug. I accidentally set nil, instead of "0", to badgeValue, and the badge still shows even after shouldHideBadgeAtZero is set as YES.
The expected behaviour should be that the badge don't show when nil value, since nil is somehow the same than 0. What do you think?
The text was updated successfully, but these errors were encountered: