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 up"up.props not defined" error in elm reactor 0.16 #438
Comments
fredcy
referenced this issue
Nov 19, 2015
Closed
"_U.list is not a function" When debugging with elm 0.16 #156
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
fredcy
Nov 20, 2015
Contributor
@evancz This problem manifests when running elm reactor in 0.16 but looks to me to be a significant problem in core/src/Native/Graphics. Some recent change added a wrapper layer in Element named _0 but there is still code around expecting to access properties like props directly from the element. Case in point is the customButton function mentioned above.
|
@evancz This problem manifests when running elm reactor in 0.16 but looks to me to be a significant problem in core/src/Native/Graphics. Some recent change added a wrapper layer in Element named |
fredcy
referenced this issue
Nov 20, 2015
Closed
Unwrap customButton inputs to get props from _0 object #440
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Is this still relevant or was it fixed by elm-lang@09f3dd2? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
It was fixed by the latter. I'm closing this now. |
fredcy commentedNov 19, 2015
The customButton native code tries to access
up.props.widthbutup.propsis not defined. Looks like an intermediate_0object was introduced betweenupand thepropsproperty.