Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upRequest: allow undefined through ports, treat it like null #476
Comments
evancz
changed the title from
Equivalence of null and undefined for ports
to
Request: allow undefined through ports, treat it like null
Jun 25, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
kspeakman
Nov 11, 2016
The maybe decoder converts undefined to Nothing, but ports do not.
This issue was referenced from another elm-discuss thread here.
kspeakman
commented
Nov 11, 2016
|
The maybe decoder converts undefined to Nothing, but ports do not. This issue was referenced from another elm-discuss thread here. |
evancz
added
the
problem
label
Jul 16, 2017
evancz
added
request
and removed
problem
labels
Mar 7, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Mar 7, 2018
Member
Tracking in elm/compiler#1687 to see if any broader patterns emerge in things people are looking for. I am wary of making things super flexible because it can start to become confusing, but I'm not 100% convinced either way.
|
Tracking in elm/compiler#1687 to see if any broader patterns emerge in things people are looking for. I am wary of making things super flexible because it can start to become confusing, but I'm not 100% convinced either way. |
mietek commentedJan 7, 2016
As mentioned on elm-discuss — can we have both
nullandundefinedcorrespond toNothing?