Closed ChristophP closed 4 years ago
Yeah, my apologies, I'm in the middle of doing some revamping right now (which includes a switch from avh4/elm-color
to tesk9/palette
) and I haven't got around to updating the examples so probably a bunch of things don't work. Give me a few days and hopefully things will be in a more consistent state =)
Sure, I am also offering my help to update the examples once the work you're doing on package code is ready. Now, that I know that avh4/elm-color
is the one that needs to go, it shouldn't be too hard to get it working.
OK, the examples should all work again now! (I appreciate the offer of help, but updating examples to use a new API is a great way to figure out problems with that API, so updating the examples has been a very useful exercise for me - and did lead to a few useful API additions.)
I still have some API changes planned, so the examples will have to be updated again soon. I'll try to keep the examples updated as I go but I apologize in advance if I forget and some of them lag behind =)
Great thanks, I will check them out soon. :-)
I'll keep in mind that they may be out of sync with the current status of the library.
Problem Files in the example folder don't compile.
Steps to reproduce
Possible Cause Namespace clashes of
tesk9/palette
(used in the package) andavh4/elm-color
(used in the example). Both export a module namedColor
.Fix I am willing to contribute a fix if that is helpful. I would need some feedback what the the best solution would be? I would propose to remove the the
avh4/elm-color
dependency. But it makes me wonder how this example ever worked? I thought dependencies with clashing module names don't ever work together because the Elm compiler cannot tell them apart.Full Output