You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've spent a few days trying to get a POC of JBrowse 1 integrated into my Angular 7 application with no luck.
An example for integrating with Angular 2+ with JBrowse 1 or 2 would be really helpful. I think the crux of the problem right now with Angular integration, is the only example posted shows that you provide main.bundle.js or browser.bundle.js in the index.html which setups up the JBrowse object immediately on page load.
In angular you dont want the JBrowse object intialized until your component is rendered. Then you want to be able to destroy that object from scope as you navigate away to a different route so that it can be recreated when your component is navigated back to.
I can setup the JBrowse object for the first time. But I get strange error messages about low level javascript objects "already being registered" when I navigate away from my JBrowse component wrapper and then navigate back to it.
Perhaps someone has already found a different work around for JBrowse and SPA applications like Angular? If so, an example would be much appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I've spent a few days trying to get a POC of JBrowse 1 integrated into my Angular 7 application with no luck.
An example for integrating with Angular 2+ with JBrowse 1 or 2 would be really helpful. I think the crux of the problem right now with Angular integration, is the only example posted shows that you provide main.bundle.js or browser.bundle.js in the index.html which setups up the JBrowse object immediately on page load.
In angular you dont want the JBrowse object intialized until your component is rendered. Then you want to be able to destroy that object from scope as you navigate away to a different route so that it can be recreated when your component is navigated back to.
I can setup the JBrowse object for the first time. But I get strange error messages about low level javascript objects "already being registered" when I navigate away from my JBrowse component wrapper and then navigate back to it.
Perhaps someone has already found a different work around for JBrowse and SPA applications like Angular? If so, an example would be much appreciated.
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions