Reference Issues
See original GitHub issueIt looks like the latest commit added a lib folder to the lib folder which threw off all the references to common in the components. Also, the PlotlyReactEditor.js file changed from plotly.js-react-editor which broke the reference in index.js
But after fixing all those references, I get the following run-time error:
TypeError: Super expression must either be null or a function, not undefined index.js:35134:113
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Autolinked references and URLs - GitHub Docs
References to URLs, issues, pull requests, and commits are automatically shortened and converted into links.
Read more >Reference issues - Linear Guide
Reference Linear issues in issue descriptions as well as comments on issues. Referencing them inline will also create a related issue in Linear....
Read more >Reference issues in your development work | Jira Software ...
To reference Jira issues while committing, building, and deploying code with Bitbucket, GitHub, or other supported developer tools: Find the issue key for ......
Read more >How to resolve Access reference issues - Office | Microsoft Learn
Provides some methods to check and resolve the reference issues in an Access database and provides some guidelines for avoiding reference ...
Read more >The Legal Issues of Reference Checking - Checkster
Learn about the legal issues of reference checking including the laws, questions you can ask, and more. Knowing the laws of reference checks...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, I understand. When I properly clean my build directory, then the files it wants are indeed missing. I’ll create a pull request from develop -> master this afternoon and ensure pieces are done shifting around.
@ereplogle I think the only answer I have is that you’ll have to sit tight for a moment. We were able to take some shortcuts to get the react component put together pretty easily and quickly, but the cost is turning out to be that hooking up the two-way coupling between the editor and the plot is turning out to be much more disruptive than I expected. I’ve pushed all of my code to the develop branches in which the editor should now show up, but in the process of straightening out those connections, the editor controls don’t currently work. My top priority at the moment is just hooking those back up. I’ll let you know as soon as that’s done.
Related is that in the process of getting things straightened out, things have shifted just a bit. In particular:
revision
and an property that needs to be hooked up. In lieu of computing full diffs,revision
helps trigger plot updates at the appropriate time.