-
Notifications
You must be signed in to change notification settings - Fork 59
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
Check to see if bundle has been loaded already. Fixes #273 #275
Conversation
Hey @Robert-Frampton, this looks good in general, I just have one question. Even though I tweaked the What is the difference between While we're at this... could we add some information in metal-soy-bundle/README.md clarifying for future reference? |
Hey @jbalsas
The reason I loaded the And yes, we can add some readme info on the build process :) |
I see... and couldn’t we trick Karma with some kind of cache querystring? &t=123? |
That's what I tried actually, didn't have any affect on it. |
c69a8cd
to
ee0c61b
Compare
Added a short description of the build process. |
Hey @Robert-Frampton, looks like this actually broke some tests when merged 😢. I'm trying to see why the merge tests are not running in Travis (only the PR ones). In the meantime, I can revert this so we can process the others, or you can send a followup PR fixing it. What would you prefer? 🤷♂️ |
Question: does the solution to the issue at hand make impossible to have multiple Metal.js versions in the same page? Hint: it’s going to happen when deploying modern bundles to portal built with different metal version. |
Hey @yuchi, that's actually a very interesting question indeed... I don't think it has ever been possible, because both We're going to revert it in any case. We can rather approach this with that in mind. It would involve touching both |
Revert "Merge pull request #275 from Robert-Frampton/metal-soy-bundle"
No description provided.