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

v0.43.0-beta.1 #5869

Merged
merged 11 commits into from
Dec 15, 2017
Merged

v0.43.0-beta.1 #5869

merged 11 commits into from
Dec 15, 2017

Conversation

jfirebaugh
Copy link
Contributor

🌞 β›° πŸŽ‰ Hi all! The next release is going to be a big one, with the marquee feature being client-side hillshading.

Before After
image image

To ensure the final release is as solid as possible, we're doing a brief beta period. Today we're releasing v0.43.0-beta.1, and we aim to release v0.43.0 in about a week. We hope you'll give the beta a spin, try out the new features, and let us know if you spot any issues. In particular, I'd like to give a shout out to recently active contributors @andrewharvey, @vicapow, @jingsam, @stevage, @bartvde, @musicformellons, and @pathmapper. Your PRs and bug reports have been great, and we'd love it if you tried out the beta.

The complete changelog follows. The release will be available on npm and the CDN shortly after this PR is merged.

0.43.0-beta.1 (December 14, 2017)

⚠️ Breaking changes

  • It is now an error to attempt to remove a source that is in use #5562
  • It is now an error if the layer specified by the before parameter to moveLayer does not exist #5679
  • "colorSpace": "hcl" now uses shortest-path interpolation for hue #5811

✨ Features and improvements

  • Introduce client-side hillshading with raster-dem source type and hillshade layer type #5286
  • GeoJSON sources take 2x less memory and generate tiles 20%–100% faster #5799
  • Enable data-driven values for text-font #5698
  • Add getter and setter for offset on marker #5759
  • Add Map#hasImage #5775
  • Improve typing for == and != expressions #5840
  • Made coalesce expressions more useful #5755
  • Enable implicit type assertions for array types #5738
  • Improve hash control precision #5767
  • supported() now returns false on old IE 11 versions that don't support Web Worker blob URLs #5801
  • Remove flow globals TileJSON and Transferable #5668
  • Improve performance of image, video, and canvas sources #5845

πŸ› Bug fixes

  • Fix popups and markers lag during pan animation #4670
  • Fix fading of symbol layers caused by setData #5716
  • Fix behavior of to-rgba and rgba expressions #5778, #5866
  • Fix cross-fading of *-pattern and line-dasharray #5791
  • Fix colorSpace function property #5843
  • Fix style diffing when changing GeoJSON source properties #5731
  • Fix missing labels when zooming out from overzoomed tile #5827
  • Fix missing labels when zooming out and quickly using setData #5837
  • Handle NaN as input to step and interpolate expressions #5757
  • Clone property values on input and output #5806
  • Bump geojson-rewind dependency #5769

@jfirebaugh jfirebaugh requested a review from mollymerp December 14, 2017 23:53
Copy link
Contributor

@mollymerp mollymerp left a comment

Choose a reason for hiding this comment

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

πŸŽ‰ thanks @jfirebaugh !

@jfirebaugh jfirebaugh merged commit 6465c04 into master Dec 15, 2017
@jfirebaugh jfirebaugh deleted the v0.43.0-beta.1 branch December 15, 2017 00:12
@stevage
Copy link
Contributor

stevage commented Dec 15, 2017

Awesome! I'm really excited - lack of good terrain styling has been the big thing I've been missing from Tilemill. (I want to re-create my old cycletour.org ).

Where is the right place to give feedback?

Also, I don't see mention of elevation-coloring (ie, green at low elevation, white at high elevation). I find it makes a huge difference for being able to visually parse a map to see where the mountains are. Is this on the radar too?

image

Oh, I also noticed this snippet comparing old hillshading and client hillshading, which others may be interested in: https://www.mapbox.com/bites/00357/

@andrewharvey
Copy link
Collaborator

elevation-coloring (ie, green at low elevation, white at high elevation).

@stevage that should be possible after #3889 hopefully.

@jfirebaugh
Copy link
Contributor Author

v0.43.0-beta.1 is now available via npm and CDN. Note that it's tagged as next rather than latest on npm, so 0.42.2 will continue to show up on the package home page.

@stevage Feedback via bug reports and feature requests as you normally would.

@vicapow
Copy link
Contributor

vicapow commented Dec 15, 2017

congrats! will take a look now

@stevage
Copy link
Contributor

stevage commented Dec 16, 2017

Is there anywhere to see documentation for the new source and layer types?

@andrewharvey
Copy link
Collaborator

andrewharvey commented Dec 16, 2017

Is there anywhere to see documentation for the new source and layer types?

@stevage I don't think it's published yet, and only the latest version of docs are hosted by Mapbox, so you'll need to run the docs locally with:

npm run start-docs

Which should show the docs at http://localhost:8080/mapbox-gl-js/style-spec

...or if you're only interested in the hillshade example you can peek at https://github.com/mapbox/mapbox-gl-js/blob/master/docs/pages/example/hillshade.html

@stevage
Copy link
Contributor

stevage commented Dec 16, 2017

Sorry, I think there's a bit of assumed knowledge here I'm missing. I don't do a lot of checking out pre-release code for local building etc. Do I need to check out the whole repo to do that? Just doing npm install mapboxgl@next && npm run start-docs didn't work.

Anyway, I think this is what I was looking for.

@andrewharvey
Copy link
Collaborator

Yeah you need to clone this repo, then either

npm install
npm run start-docs

or

yarn install
yarn run start-docs

The HTML docs are much nicer than the style spec JSON, but it's your preference πŸ˜‰

@vicapow
Copy link
Contributor

vicapow commented Dec 17, 2017

Sorry, for the delay in responding. The beta seems to be working fine for me. Will continue to use it and report back if there's issue. Nicely done!

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.

9 participants