search

liqula / react-hs

A GHCJS binding to React based on the Flux design. The flux design pushes state and complicated logic out of the view, allowing the rendering functions and event handlers to be pure Haskell functions.
32 stars 10 forks source link

Cannot build the react-hs-examples sub-project #52

Open pamu opened 7 years ago

pamu commented 7 years ago

[react-hs-examples] stack build

Ignoring that the GHCJS boot package "aeson" has a different version, 1.1.1.0, than the resolver's wanted version, 1.0.2.1

[react-hs-examples] stack build

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for react-hs-0.1.0:
    ghcjs-base must match -any, but the stack configuration has no specified version
needed due to react-hs-examples-0.1.0 -> react-hs-0.1.0

In the dependencies for react-hs-examples-0.1.0:
    ghcjs-base must match -any, but the stack configuration has no specified version

Plan construction failed.
fisx commented 7 years ago

sorry for the delay. we try to respond to issues within 24h, but sometimes we run out of day before we're done with all the work. (-:

you're posting two sections with the same heading, is that a typo?

what are the steps you performed to get you to the two errors, resp.?

the aeson boot package version conflict is harmless (due to the fact that ghcjs uses patched clones of upstream libraries like aeson, should be fixed, but meanwhile it is unlikely to do any harm).

the second one is obviously not so harmless. i remember having seen and helped fixing it, but i don't remember the details. possibly something about the wrong cabal version? @danse do you remember this one?

fisx commented 7 years ago

thanks @pamu for reporting this. when resolved, we should add this to the README.

danse commented 7 years ago

Hi. I don't remember that error, and i'm afraid that we won't get much further without more feedback from @pamu. I didn't try to build the examples

danse commented 7 years ago

I can build the todo example.

The docs are a bit outdated and confusing. In practice i ran stack build and make in the todo folder and than browsed todo/html/todo.html. There was a runtime error so i had to run npm install that for some reason was omitted by the Make run. After installing, the todo worked like a charm.

So summarising, @pamu disappeared and we have no idea about what their problem was, but the doc and Makefile might use some love. I can prepare a pull request if you consider the doc change a valid resolution of this issue.