Skip to content

Data.Record conflict - module defined both in purescript-records and purescript-record #14

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

Closed
luntain opened this issue Oct 6, 2017 · 2 comments

Comments

@luntain
Copy link

luntain commented Oct 6, 2017

I ran into it by using purescript-quickcheck with purescript-reactnative. The former depends on purescript-record and the latter on purescript-records.

@dmbfm
Copy link

dmbfm commented Oct 23, 2017

I was able to fix this issue by using

"purescript-records": "git://github.com/athanclark/purescript-records#214a78e65feda4328ab7245ed8edb10b9b8dd0d8",
"purescript-record": "^0.2.3"

in the bower.json file in my fork of purescript-reactnative. I guess we have to wait until these PRs are merged:

purescript/purescript-record#7
doolse/purescript-records#2

@doolse
Copy link
Owner

doolse commented Nov 8, 2017

In 5.0.0 instead of relying on purescript-records it now just has it's own Optional class. Eventually when purescript-record has the required functionality it'll depend on that.

@doolse doolse closed this as completed Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants