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

Ensure generated composite function stops are in the correct order #4509

Merged
merged 2 commits into from
Mar 28, 2017

Conversation

anandthakker
Copy link
Contributor

This fixes a bug in the generated stops used by the implementation of composite
functions, wherein zoom stops were sorted lexicographically rather than
numerically.

Anand Thakker added 2 commits March 28, 2017 09:48
This captures a bug in the generated stops used by the implementation of
composite functions, wherein zoom stops were sorted lexicographically
rather than numerically.
Iterating over zoom levels as object keys did not guarantee ordering,
and resulted in, e.g. the stop for 2.1 coming after the one for 3
@anandthakker anandthakker merged commit 8061723 into master Mar 28, 2017
@anandthakker anandthakker deleted the fix-sort-stops branch March 28, 2017 16:36
lucaswoj pushed a commit that referenced this pull request Mar 29, 2017
…4509)

* Test composite function w/ int & fractional stops

This captures a bug in the generated stops used by the implementation of
composite functions, wherein zoom stops were sorted lexicographically
rather than numerically.

* Ensure generated composite function stops are in the correct order

Iterating over zoom levels as object keys did not guarantee ordering,
and resulted in, e.g. the stop for 2.1 coming after the one for 3
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.

2 participants