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 upUpgrade from elm core 4.0.2 to 4.0.4 breaks Ports #683
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Aug 8, 2016
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Aug 8, 2016
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Include an http://sscce.org/ |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
cscalfani
Aug 8, 2016
Okay, so I realized that the problem had to do with how I was building the app. Not sure why an upgrade to 4.0.4 changed the behavior that was working just fine all last week. Don't really care because I've changed my build process.
Sorry for the false alarm.
cscalfani
commented
Aug 8, 2016
|
Okay, so I realized that the problem had to do with how I was building the app. Not sure why an upgrade to 4.0.4 changed the behavior that was working just fine all last week. Don't really care because I've changed my build process. Sorry for the false alarm. |
cscalfani
closed this
Aug 8, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Aug 8, 2016
Member
No worries, glad it is working again!
(It may have been about assets getting stuck in elm-stuff/build-artifacts/ which will get fixed via some elm-make improvements.)
|
No worries, glad it is working again! (It may have been about assets getting stuck in |
cscalfani commentedAug 8, 2016
I now need to import Json.Decode and Json.Encode for my port module. If omitted, the compiler doesn't produce an error. Instead I get the dreaded Runtime Error:
ReferenceError: _elm_lang$core$Json_Decode$string is not defined