summaryrefslogtreecommitdiff
path: root/platform/node
Commit message (Collapse)AuthorAgeFilesLines
* [node] release 4.1.0node-v4.1.0Konstantin Käfer2018-10-101-1/+1
|
* [node] release 4.1.0-pre.1node-v4.1.0-pre.1Konstantin Käfer2018-10-041-2/+4
|
* [ios, macos, android, node] update changelogsMolly Lloyd2018-10-031-0/+1
|
* [core] Do not constrain on X axis in ConstrainMode::HeightOnlyBruno de Oliveira Abinader2018-10-021-6/+3
|
* [test] Bump gl-js pin.Chris Loer2018-09-191-2/+12
|
* [android, ios, macos, node] Update CHANGELOGsJohn Firebaugh2018-09-131-0/+1
|
* [core] Make "to-number" of null behave as documentedJohn Firebaugh2018-09-131-0/+1
|
* [tests] Update mapbox-gl-jsJohn Firebaugh2018-09-131-2/+2
|
* [node] v4.0.0John Firebaugh2018-09-131-1/+13
|
* [node] Ignore custom layer tests in node platformAnder Conselvan de Oliveira2018-09-131-0/+2
| | | | | Custom layers are not implemented in node platform so ignore tests that require it.
* [node] Release cadence for npm packageJohn Firebaugh2018-09-121-4/+6
|
* [core] Port "collision group" plumbing to gl-native.Chris Loer2018-09-125-7/+23
| | | | | [node] Hook up map-wide "crossSourceCollisions" option, defaulting to true. [test] Pass "crossSourceCollisions" test option through test harness; enable cross-source-collisions tests on native.
* Port symbol-z-order symbol layout style-spec property to Nativeupstream/sort-by-yryanhamley2018-09-071-0/+1
|
* [ios, node, macos, android] update changelogs for feature expression supportMolly Lloyd2018-08-311-0/+1
|
* [test] ignore legacy expression testsMolly Lloyd2018-08-311-0/+50
|
* [windows, qt] fix windows compiler errors, remove tao + tuple polyfillMolly Lloyd2018-08-311-0/+1
|
* [core] Implement CrossFadedDataDrivenProperty to add support for feature ↵Molly Lloyd2018-08-311-0/+3
| | | | expressions in `*-pattern` properties
* [node] capture invalid input data as `ParseError` objectsKonstantin Käfer2018-08-273-5/+43
| | | | This allows us to distinguish them from other types of errors
* [core] Add `line-gradient` propertyMikhail Pozdnyakov2018-08-231-2/+0
| | | | | | | | Porting of https://github.com/mapbox/mapbox-gl-js/pull/6303 See the link above for the description of the feature and its limitations). Based on patch from @lbud (Lauren Budorick).
* [core, test] Bump GL JS pin to bring gl-native back in sync with gl-js.Chris Loer2018-08-211-0/+12
| | | | | Requires changing `generate-style-code` to treat 'formatted' as being the same as 'string' until gl-native gets 'formatted' support with https://github.com/mapbox/mapbox-gl-native/pull/12624. To make nitpick happy, PropertyFunction.java uses the latest "text-field" description from v8.json. It's technically correct, just kind of pointless since the "If a plain `string` is provided" clause will always be true.
* [core] make style/conversion.hpp implementation privateKonstantin Käfer2018-08-192-2/+2
|
* [core] Fix querying for annotations near tile boundaries at high zoom.Chris Loer2018-08-141-0/+1
| | | | | | | | Fixes issue #12472. This commit doesn't address the underlying issues that come from symbolAnnotationTree using a slightly lower precision coordinate system than the annotations themselves. Instead, it just puts a small padding around each tile when it queries for tile data, so that symbols right at the tile boundary will be included in both tiles. The rendering/querying code will take care of only displaying one instance. The padding is in global coordinates, so at higher zoom the padding will be larger in tile units -- this is consistent with precision loss also being greater at higher zoom.
* [core] Don't default-show text/icons that depend on the placement of a ↵Chris Loer2018-08-131-0/+1
| | | | | | paired icon/text Fixes issue #12483.
* [core] Eliminate setProperty & co.John Firebaugh2018-08-131-2/+2
|
* [docs] Changelog entries for symbol-placement: line-centerChris Loer2018-08-131-0/+1
|
* [build] Update gl-jsJohn Firebaugh2018-08-084-44/+38
|
* [node] Update documentation for publishing process (#12500)John Firebaugh2018-07-311-5/+11
| | | | | | * Update node publishing process * publish instruction separated into steps
* [build] Remove obsolete bitrise.yml filesJohn Firebaugh2018-07-241-15/+0
|
* [test] Add native ignore for symbol-cross-fade test.Chris Loer2018-07-231-0/+1
|
* [node] prevent scheduled renderFinished() calls from running when render is ↵Konstantin Käfer2018-07-131-9/+16
| | | | | | | | | | | | | | | | | canceled Reverts d5aff71 (#11948) and implements an alternative solution. Even with the previous fix applied, we were calling `renderFinished()` directly when the render was canceled. This led to the following scenario (all on the main thread): - `Map::renderStill()` callback is called, `uv_async_send` schedules a call to `renderFinished()`. - `NodeMap::cancel()` destroys the map object, and calls `renderFinished()` directly, which cleans up the request - `NodeMap::startRender()` is called to schedule a _new_ render, which means that a new callback will be set - The `uv_async_t` fires and calls `renderFinished` again: - We don't return early as intended by the fix in #11948 since a new callback/`req` object is now available. - Since neither error nor image has been set, we'll see a `Didn't get an image` error message. - We call the callback with the error. In scenario where we're reusing Map objects, we will start a new render, which will now trigger the `Map is currently rendering an image` error in `Map::renderStill`, and the map object enters a circle in which it will now fail repeatedly with this error. This commit fixes the issue by completely removing the existing `uv_async_t` handle that could have a scheduled call, and replacing it with a fresh instance of an `uv_async_t` handle.
* [docs] Add changelog entries for #12294Chris Loer2018-07-051-0/+1
|
* [core] Fix sort order for queryRenderedFeatures when features are filtered.Chris Loer2018-07-031-2/+0
| | | | Fixes issue #12104.
* [ios, macos] Try to make darwin "resolvedLocale" BCP 47 compliantChris Loer2018-07-031-1/+1
|
* [test] Remove "collator" ignoresChris Loer2018-07-031-15/+1
|
* [core] Introduce "collator" expressionsChris Loer2018-07-031-0/+8
| | | | Cross platform parsing and evaluation code.
* Change error message with invalid render usage (#12265)Dane Springmeyer2018-06-292-2/+2
| | | | | | | | * Change error message with invalid render usage This change disambiguates this error condition with a different error with the same error message at https://github.com/mapbox/mapbox-gl-native/blob/789baf4c1f252071bf58e689e050b34eb2656363/src/mbgl/map/map.cpp#L157-L160 * fix test expectation
* [tests] Replaced the ZoomHistory test with a render testJohn Firebaugh2018-06-281-0/+2
|
* [tests] Remove ignores for implemented featuresJohn Firebaugh2018-06-271-27/+3
|
* [node] Build and publish for node 6.x, 8.x, and 10.xJohn Firebaugh2018-06-262-17/+22
| | | | Note that we're still only testing the 6.x ABI (48).
* [node] add compatibility with node-pre-gyp binary publishingKonstantin Käfer2018-06-261-1/+1
|
* [core] add raster-resampling property (#12176)upstream/rcleeMolly Lloyd2018-06-211-0/+4
| | | | | | | | | | * update style-code for raster-resampling * implement user-defined raster-resampling * invert filter condition * raster-resampling -> raster-resampling-mode for darwin language conventions
* [core] port zero line-width fix from gl-js (#12175)Molly Lloyd2018-06-191-0/+6
| | | | | | | | * port zero line-width fix from gl-js * ignore transition test * ignore feature-state tests
* [node] hide all symbols from the Node.js addonsKonstantin Käfer2018-06-042-0/+3
|
* [node] fixup bad mergeKonstantin Käfer2018-05-221-1/+1
|
* [node] allow building all ABIs at onceKonstantin Käfer2018-05-221-2/+1
|
* [node] move to Nan 2.10.0Konstantin Käfer2018-05-224-14/+33
|
* [node] prevent race condition for renderFinishedKonstantin Käfer2018-05-221-0/+6
|
* [core] Align match behavior with case/==John Firebaugh2018-05-181-0/+3
| | | | Makes `["match", ["get", k], label, match, otherwise]` equivalent to `["case", ["==", ["get", k], label], match, otherwise]`. This changes the behavior of match expressions where the runtime type of the input does not match the type of the labels: previously such expressions produced a runtime type error and then fell back to the property default value; now they produce the fallback value from the match expression.
* [core] Rework spec function/expression taxonomyLauren Budorick2018-05-141-1/+7
| | | Ports https://github.com/mapbox/mapbox-gl-js/pull/6521, updating codegen scripts to parse new expression taxonomy.
* [docs] Make per-platform installation docs self-containedJohn Firebaugh2018-04-302-4/+7
| | | | I've seen several issues where users followed platform-specific install docs, but were unaware of additional prerequisites spelled out in the top-level INSTALL.md. So let's try making each platform's installation documentation self contained.
View Lorry Controller Status