Skip to content
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

@storybook/addon-comments v3.0.0 falls with error #1190

Closed
dangreen opened this issue Jun 5, 2017 · 8 comments
Closed

@storybook/addon-comments v3.0.0 falls with error #1190

dangreen opened this issue Jun 5, 2017 · 8 comments
Assignees
Milestone

Comments

@dangreen
Copy link

dangreen commented Jun 5, 2017

VM9775 manager.bundle.js:94268 Uncaught TypeError: Cannot read property 'persister' of null
    at Container.init (VM9775 manager.bundle.js:94268)
    at Container.componentDidMount (VM9775 manager.bundle.js:94243)
    at VM7843 manager.bundle.js:28100
    at measureLifeCyclePerf (VM7843 manager.bundle.js:27910)
    at VM7843 manager.bundle.js:28099
    at CallbackQueue.notifyAll (VM7843 manager.bundle.js:11842)
    at ReactReconcileTransaction.close (VM7843 manager.bundle.js:32993)
    at ReactReconcileTransaction.closeAll (VM7843 manager.bundle.js:5946)
    at ReactReconcileTransaction.perform (VM7843 manager.bundle.js:5893)
    at batchedMountComponentIntoNode (VM7843 manager.bundle.js:12750)
@dangreen
Copy link
Author

dangreen commented Jun 5, 2017

also

VM9775 manager.bundle.js:93970 Uncaught TypeError: Cannot read property 'persister' of null
    at DataStore._loadUsers (VM9775 manager.bundle.js:93970)
    at VM9775 manager.bundle.js:93917

@tmeasday
Copy link
Member

tmeasday commented Jun 6, 2017

Hi @dangreen, thanks for reporting this. I just confirmed this with both the test-cra app and a vanilla CRA app.

The issue is the lack of a database package. See #1145.

I'm not totally sure how it worked before, or how to best move forward @ndelangen, but at the least we should indicate this problem on the comments addon for now.

@tmeasday tmeasday added this to the v3.2.0 milestone Jun 23, 2017
@tmeasday
Copy link
Member

@ndelangen -- what are your thoughts here?

@shilman
Copy link
Member

shilman commented Jun 23, 2017

@tmeasday @ndelangen let's get rid of comments in 3.2! 👍

@tmeasday
Copy link
Member

@ndelangen confirmed to me he agrees we should remove it! If anyone objects, now would be a good time :)

@ndelangen
Copy link
Member

Remove it, we will rebuild something like it when the time comes.

@jakiestfu
Copy link

I'm interested in this comments addon. Was the consensus to not work on this for the time being? What needs to be done?

@ndelangen
Copy link
Member

@jakiestfu I don't think we want to write custom connectors for all sorts of databases or chat apis... I'm not 100% sure on this, but it's how I feel about it now.

Of course I wouldn't stop anyone from writing such a thing, though we'd have to argue to add it to the core repo or not.

I'm not sure there's consensus about it, I'm personally a little divided on the issue, to be honest.

I have mentioned in the past that I think a good minimal viable solution would be to embed a system like https://disqus.com/ into an panel, what are your thoughts on that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants