-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use purescript-d3 on current purescript #20
Comments
I am too new to purescript, javascript, or d3 in general to fix this myself, however I'm happy to consider writing a patch if someone is willing to critically review it and fix the inevitable mistakes. The actual fixes seem to involve mainly a simple matter of adding types to all the 17 functions. This also probably depend the status of #17 however I wouldn't know what the impact of those changes would be here. Some guidance would be appreciated. |
Other than the warnings, think this just needs tagged as release, seems to be working fine for me on 0.9.x - @pelotom would you mind tagging? Maybe also worth pushing to pursuit. |
Tagged the latest. I'm happy to take a PR which addresses the warnings. |
Also published to Pursuit |
can this be added to https://github.com/purescript/package-sets |
I think they may have broken it again. I was hoping to learn purescript this evening with d3 as the first library I wanted to use, but once I got it loaded as a package set, it failed with:
|
When I do the following:
I get conflicting dependencies as follows:
And neither of these options work.
I suspect that using the master branch will work, however bower currently seems to use v0.7.0, which still exhibits this issue.
Update: Yes, using the master build does work, although it builds with 17 warnings, all of which are much the same:
The text was updated successfully, but these errors were encountered: