Skip to content
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

Scattermapbox BADNUM + [email protected] #1543

Closed
wants to merge 6 commits into from

Conversation

etpinard
Copy link
Contributor

to be merged in #1538 - fixing the test failures there.

In brief, this PR:

  • makes scattermapbox/calc.js reuse scattergeo/calc.js ♻️
  • 🔪 the last remaining signs of calcdata placeholder
  • bumps mapbox-gl to ^0.33.1. Among a few interesting performance improvements, this new version allows use the identity property function which 🔪 the hacky stops logic in scattermapbox/convert.js 🎉

Important

  • [email protected] does not get along with the nw.js version we use in our image test container (same as on the plot.ly image server) - see here for more details. This is probably a good time to bump the nw.js version. The latest nw.js version is 0.21.4 while we're still using 0.12 cc @bpostlethwaite

  • Note that I couldn't update mapbox-gl to their latest version (v0.34.0) because that version is currently broken in browserified bundles and that patch hasn't been published yet.

- to improve performance in check downstream
- add calc tests to scattergeo_test.js
- to determine if calcdata item should be skipped
- 🔪 scattermapbox/calc.js, reuse scattergeo/calc.js instead!
- this makes calcdata items 1-1 with fullData coords
  (as all our other trace types)
- Use identity function type in properties (available since 0.26.0)
  to replace brutal hack with `stops` 🎉
@etpinard etpinard added status: reviewable bug something broken labels Mar 31, 2017
@etpinard etpinard added this to the v1.26.0 milestone Mar 31, 2017
@etpinard etpinard mentioned this pull request Mar 31, 2017
if(!Array.isArray(cd) || !cd[0]) {
cd = [{x: false, y: false, placeholder: true}];
cd = [{x: false, y: false}];
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we turn this into [{x: BADNUM, y: BADNUM}] or are we not quite ready for that yet?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call. Let me try that!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done in b5cd573

Didn't break any tests. The only place I can think of that this would impact in the legend code, but looks like it isn't making any assumptions on x / y here.

@alexcjohnson
Copy link
Collaborator

This looks great! Really nice simplification. Lets get the nw version bumped so we can get all images tested before merging this, but other than that 💃 !!

@etpinard
Copy link
Contributor Author

etpinard commented Apr 7, 2017

Replaced by #1564

@etpinard etpinard closed this Apr 7, 2017
@etpinard etpinard deleted the scattermapbox-badnum branch April 7, 2017 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants