Skip to content

Conversation

@jdfreder
Copy link
Contributor

It doesn't make sense to to clobber the require.js globals that live in the notebook for Plotly's offline mode. Nor does it make sense to load the Plotly JS from the CDN when running in offline mode. This PR uses requirejs named definitions and requirejs commonjs support to embed the plotly JS on the page.

This PR does not solve the workflow of getting the plotly.js build into the plotly.py repo. In a separate PR that should be automated.

related to #408
closes #373

@etpinard
Copy link
Contributor

Looks great to me. Thanks 🍻 .

I'll let @cldougl / @chriddyp / @theengineear give this a final review.

@theengineear
Copy link
Contributor

Thanks @jdfreder! Looks great to me too!

Can you add a Fixed line to the Unreleased section of our CHANGLOG.

We can bump the version and release shortly after.

@jdfreder
Copy link
Contributor Author

Can you add a Fixed line to the Unreleased section of our CHANGLOG.

✔️

@theengineear
Copy link
Contributor

Excellent! Thanks! I'm good to merge, @chriddyp, sound good?

@chriddyp
Copy link
Member

looks good!

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

Successfully merging this pull request may close these issues.

qgrid - plotly conflict

4 participants