Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix: react to config changes #6395

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

Closed
archmoj wants to merge 5 commits into master from config-react
Closed

Fix: react to config changes #6395

archmoj wants to merge 5 commits into master from config-react

Conversation

Copy link
Contributor

@archmoj archmoj commented Dec 14, 2022

Fixes #6394.

@plotly/plotly_js

Copy link
Collaborator

Nice! Maybe then just a test like this one but for cartesian?

it('can put polar plots into staticPlot mode', function(done) {

Copy link
Contributor Author

archmoj commented Dec 21, 2022
edited
Loading

@alexcjohnson I don't recall what noCIdep was about. ̄\_(ツ)_/ ̄
After the changes proposed in this PR, it looks like we need to adjust the cartesian test right above the line you mentioned.

Copy link
Collaborator

@noCIdep came in here: 623146f91c

 // Although not recommended, some tests "depend" on other
 // tests to pass (e.g. the Plotly.react tests check that
 // all available traces and transforms are tested). Tag these
 // with @noCIdep, so that
 // - $ npm run test-jasmine -- tags=noCI,noCIdep
 // can pass.

So looks like on CI it's ignored, but it marks tests that need to run so the noCI tests succeed. Quite possibly obsolete by now, you could try running just npm run test-jasmine -- tags=noCI and see if it works?

And good call, I somehow hadn't noticed the cartesian test right above that 😅 But that test was already passing, right? So what can we add to that test that would have broken before this change but now works correctly?

@gvwilson gvwilson self-assigned this May 27, 2024
@gvwilson gvwilson removed their assignment Aug 2, 2024
@gvwilson gvwilson added fix fixes something broken P1 needed for current cycle and removed status: has TODOs bug something broken labels Aug 8, 2024
@gvwilson gvwilson added the cs customer success label Aug 21, 2024
@archmoj archmoj added this to the v3.0.0 milestone Oct 2, 2024
@archmoj archmoj modified the milestones: v3.0.0, v4.0.0 Nov 7, 2024
@archmoj archmoj added P3 backlog and removed P1 needed for current cycle labels Nov 7, 2024
@gvwilson gvwilson assigned gvwilson and unassigned archmoj Nov 20, 2024
@archmoj archmoj changed the title (削除) react to config changes (削除ここまで) (追記) Fix: react to config changes (追記ここまで) Nov 22, 2024
@gvwilson gvwilson added P1 needed for current cycle and removed P3 backlog labels Jul 10, 2025
@archmoj archmoj removed this from the v4.0.0 milestone Jul 15, 2025
Copy link
Contributor Author

archmoj commented Jul 17, 2025

Reworked in #7475.
Closing.

@archmoj archmoj deleted the config-react branch July 24, 2025 19:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Labels
cs customer success fix fixes something broken P1 needed for current cycle
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

enable updating the config of a plot without changing other parameters

AltStyle によって変換されたページ (->オリジナル) /