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
{{ message }}
This repository has been archived by the owner on Apr 25, 2021. It is now read-only.
Our current implementation gives browser.lessThan.landscape a false value which is not quite right. Maybe this is a good usecase for setting the value to undefined?
The text was updated successfully, but these errors were encountered:
For the project I'm currently working on, we've leaned heavily on leaving items undefined where possible (though Redux gets in the way of that somewhat) because (a) we're using react-redux and supplying everything as destructured props, and (b) we're using Typescript/ES6, so it's extremely easy to have inline defaults inside a component for undefined items from the Redux state (but not for null ones).
However, the "official" approach for Redux seems to be to set things null and never use undefined, to the point of it refusing to accept undefined values from normal reducers.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our current implementation gives
browser.lessThan.landscape
a false value which is not quite right. Maybe this is a good usecase for setting the value toundefined
?The text was updated successfully, but these errors were encountered: