summaryrefslogtreecommitdiff
path: root/platform/node
Commit message (Collapse)AuthorAgeFilesLines
* [core] Don't use exceptions in MapObserver::onDidFailLoadingMapAnder Conselvan de Oliveira2019-03-132-5/+10
| | | | | | | Using different exception pointers to specify the loading failure makes an awkward API. Most users rethrow the exception only to figure out what type of error happened so it can be reported properly. So replace the exception pointer with a enum an string description of the failure.
* [node] Change Map/FileSource relationship to compositionBruno de Oliveira Abinader2019-03-122-12/+27
|
* [core, node] Use es5 syntax for imports in expressions testsAlexander Shalamov2019-03-111-3/+3
| | | | | Instead of forcing ES6 module syntax, at this point, it is less distruptive to fix expression tests to use ES5 import syntax.
* Revert "[core] Use ES6 import / export syntax for node test harness"Alexander Shalamov2019-03-114-12/+12
| | | | This reverts commit c6598fc5da063f9b60204639cd619647cbbc89da.
* [core] Add MapOptions to define properties of MapSudarsana Babu Nagineni2019-03-081-8/+10
| | | | | | To simplify the Map constructor, introduce MapOptions interface to define the properties that can be set on a Map.
* [core] consolidate Axonometric rendering APISudarsana Babu Nagineni2019-03-081-13/+12
| | | | | | | Instead of having individual APIs for setting axonometric and skew options, create ProjectionMode struct that holds all the relevant options for Axonometric rendering and introduce setter/getter on the Map for those options.
* [core] Use ES6 import / export syntax for node test harnessAlexander Shalamov2019-03-084-12/+12
|
* Update mapbox-gl-js submodule to v0.53.0Mikhail Pozdnyakov2019-03-061-1/+37
|
* Skip failing render testsMikhail Pozdnyakov2019-03-051-1/+5
|
* [core] Remove map coordinate setters/gettersBruno de Oliveira Abinader2019-03-041-1/+1
|
* [core] Transform{State}: s/angle/bearing/Bruno de Oliveira Abinader2019-03-041-2/+2
|
* [core] Remove map bearing setters/gettersBruno de Oliveira Abinader2019-03-041-1/+1
|
* [core] Remove map pitch setters/gettersBruno de Oliveira Abinader2019-03-041-1/+1
|
* [core] Remove map zoom setters/gettersBruno de Oliveira Abinader2019-03-041-1/+1
|
* remove some outdated integration test ignores (#13800)Vladimir Agafonkin2019-01-281-5/+0
|
* [core] Do not consider X axis when constraining scaleBruno de Oliveira Abinader2018-11-291-0/+2
|
* [build] Update to geometry v1.0.0Bruno de Oliveira Abinader2018-11-131-2/+6
|
* Consolidate `style::Layer` properties APIMikhail Pozdnyakov2018-10-251-26/+1
| | | | | | | | The `style::Layer` class now exposes all the properties contained at `style::LayerImpl`. This allowed to drop `style::Layer::accept()` method usage, avoid the repeated generated code and thus save some binary size. This patch is a part of the layers modularization effort.
* [core] remove some uses of <iostream> and <sstream>Konstantin Käfer2018-10-231-2/+2
|
* [core] CameraOptions receives and outputs angle and pitch as degrees, not ↵Bruno de Oliveira Abinader2018-10-191-2/+2
| | | | radians
* [Core] Ensure queryRenderedFeatures accounts for icon-rotate (#13105)Ryan Hamley2018-10-181-1/+0
|
* [core] Initial implementation of 'format' expressionChris Loer2018-10-152-17/+32
|
* [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.
View Lorry Controller Status