Merge "mapbox-gl-style-spec" repository into this repository #3946
Commits on Jan 7, 2016
Commits on Jan 11, 2016
Commits on Jan 13, 2016
-
Avoid large disjunctions when evaluating 'in'
V8 is unable to evaluate large disjunctions, failing with "RangeError: Maximum call stack size exceeded". Fixes #1782
-
Commits on Jan 14, 2016
Commits on Jan 20, 2016
Commits on Jan 29, 2016
Commits on Feb 3, 2016
Commits on Feb 5, 2016
-
Revert "prevent ramp from having duplicate stops"
This reverts commit e37aa5f. Adding validation of ramp stops was good in spirit, but it breaks some v8 styles. Reverting until v9 where we can make backwards incompatible changes.
-
Merge pull request #413 from mapbox/ramp-validation
Revert "prevent ramp from having duplicate stops"
Commits on Feb 8, 2016
Commits on Feb 9, 2016
Commits on Feb 19, 2016
-
-
Fix an issue where 'in' '$type' drops features
If 'Point' is listed inside an 'in' facet on the '$type' property as the last value when all geometry types are listed, it will be ignored. `indexOf` accepts multiples params and `map` emits multiple params. Only the first param from map should be passed to indexOf. The order of 'Point' in the arrays ends up causing the value not to be found and the index in the compiled filter to be -1. Using a proper inline function solves the issue.
-
Merge pull request #14 from mapbox/in-types
Fix an issue where 'in' '$type' drops features
Commits on Feb 24, 2016
Commits on Mar 7, 2016
Commits on Mar 17, 2016
Commits on Mar 30, 2016
Commits on Apr 6, 2016
Commits on Apr 12, 2016
Commits on Apr 13, 2016
Commits on Apr 19, 2016
Commits on Apr 26, 2016
Commits on Apr 27, 2016
Commits on May 3, 2016
Commits on May 5, 2016
-
Merge pull request #451 from mapbox/has
Add support for has / !has operators
Commits on May 16, 2016
-
Update function documentation and validation for property functions (#…
…450) * Validate support for property functions * Add npm start script * Update function docs * fixup! Update function docs * Update index.html
Commits on May 17, 2016
-
-
More explicit instruction around sources and layers. (#454)
* More explicit instruction around sources and layers. * Update index.html
-
Add external geojson source example (#455)
* Add external geojson source example * Update index.html
Commits on May 31, 2016
-
change function type "continuous" to "exponential" (#457)
It seems to be exponential according to project https://github.com/mapbox/mapbox-gl-function
-
-
Commits on Jun 1, 2016
Commits on Jun 6, 2016
-
* Upgrade to Jekyll 3 * Updated docs/_layouts/default.html
Commits on Jun 11, 2016
Commits on Jun 13, 2016
Commits on Jun 15, 2016
-
Add icon-text-fit, icon-text-fit-padding (#461)
* First pass at icon-text-fit, icon-text-fit-padding properties * Support specifying padding independently on all 4 sides
Commits on Jun 23, 2016
Commits on Jul 1, 2016
-
Annotate reference and documentation with SDK requirements
Each layer type and property is annotated with the first version of the JS, iOS, and Android SDK that supports the feature. For properties, support is divided into basic support and data-driven styling support. Absence of an annotation for a particular SDK implies that the feature is unsupported. Unsupported combinations are marked as such and in some cases linked to the relevant GitHub issue. Most features are annotated as supported starting with GL JS 0.10.0, iOS SDK 2.0.0, and Android SDK 2.0.1 -- the first stable releases that supported GL rendering of the initial v8 style specification. The exceptions are the following: Source support: * Image and Video sources * GeoJSON clustering Properties added to v8 after the initial release: * line-offset * text-pitch-alignment * icon-text-fit * icon-text-fit-padding Properties where data-driven styling support has been introduced in GL JS: * circle-opacity * circle-blur * fill-color * fill-outline-color * circle-color * circle-radius Filter operators are not yet annotated. The interesting operator is `has`/`!has`, which was a recent introduction.
-
-
"Mapbox GL Style Specification" ⇢ "Mapbox Style Specification"
Remove other references to "GL" and perform general editing.
Commits on Jul 5, 2016
Commits on Jul 13, 2016
-
-
Document the supported range of geometric coordinates in vector tiles (…
…#468) * Document the supported range of geometric coordinates in vector tiles * Update index.html * Update index.html
Commits on Jul 14, 2016
Commits on Jul 15, 2016
Commits on Jul 16, 2016
-
as discussed in mapbox/earcut#65
Commits on Jul 18, 2016
Commits on Jul 19, 2016
Commits on Aug 1, 2016
Commits on Aug 24, 2016
-
Specify bearing and pitch direction (#482)
Amended the bearing and pitch property documentation to describe some reference points, based on how Mapbox GL interprets these properties.
Commits on Aug 25, 2016
Commits on Aug 27, 2016
-
Dynamically include source property docs (#483)
* Dynamically include source property docs * Omit type and vector.tileSize
Commits on Sep 8, 2016
-
Ignore layout and paint properties for invalid layers (#490)
Currently, if a style contains an invalid layer type and either a paint or layout property for that layer, the style validator will throw. Instead of throwing, these properties should be ignored, the layer type will still be reported as an error.
-
Commits on Sep 19, 2016
-
Sketch of removing spec-defined default value for text-rotation-align…
…ment given that its renderer-defined defaults are more complex.
-
-
Introduce new default enum value for text and icon rotation and pitch
This adds a new enumeration value called `auto` for text-rotation-alignment, icon-rotation-alignment and text-pitch-alignment. The new value is set as the default for the three properties it was added to and the associated `doc` description was updated to reflect that. In addition, the relevant SDK support tables have been updated to reflect the first expected native SDK releases that'll support the new `auto` value. The js SDK version was not updated since the value was not known at the time of this commit. It can be updated in the future.
-
Generate sdk support rows from spec JSON
This adds logic to loop through all of the values in `sdk-support` and render the appropriate documentation for each of them. There are special cases for `basic` -> "Base" and to ignore `property-function` since that is already handled as a special case and has an associated bool value at the root level of each item's object in the spec.
-
This will cause it to become MGLTextPitchAlignmentAuto when the iOS/macOS SDK documentation is automatically generated from this file.
-
-
-
Remove sdk support and enhance doc description for auto
This updates the doc descriptions for text-rotation-alignment and icon-rotation-alignment so that auto has a meaning in the system (as a default). This also removes all SDK support for auto. Once support for auto lands in GL JS and GL native then the specific version numbers can be added back.
-
-
Commits on Sep 21, 2016
Commits on Sep 22, 2016
Commits on Sep 23, 2016
Commits on Sep 27, 2016
Commits on Sep 30, 2016
-
fixes #497: document enum values (#510)
Adds `doc` property to all enum `values`, moving them from JSON arrays to objects. Downstream mobile SDK work in mapbox/mapbox-gl-native#6508. Downstream Studio work in mapbox/studio#7765. Fixes a typo in `icon-text-fit`. Also updates validation, docs generation, and tests.
Commits on Oct 4, 2016
-
Add identity function type (#512)
* Add identity function type * Validate that identity functions do not have stops
-
Commits on Oct 5, 2016
-
Support a `colorSpace` property on functions that allows users to choose LAB or HCL color interpolation.
-
Add colorSpace enum property to functions to enable color space aware…
… interpolation (#515)
-
Commits on Oct 7, 2016
-
Fix mistake during release of 8.9.0 (#518)
I accidentally published the `HEAD` of the `identity-function` branch to `npm` as version `8.9.0` in mapbox/mapbox-gl-style-spec@d7975ae0f6e9da2cd5 67c8172fe7867f204509a3. Fortunately, I did merge `identity-function` into `master` first. With this commit restoring some state in `mb-pages`, we should be able to continue forward without ill effect.
Commits on Oct 11, 2016
Commits on Oct 14, 2016
-
Update SDK support for v0.26.0, facelift for function section (#537)
* Update SDK support for v0.26.0, facelift for function section * Revert silly changes * Update index.html
-
-
Use categorical type by default when input values are strings (#29)
* Use categorical type by default when input values are strings This reverts commit 81488ab. * Update tests
Commits on Oct 20, 2016
-
-
Deprecate "interactive" property (#544)
* Deprecate "interactive" property fixes #541 * Add test to assert that layers with deprecated 'interactive' property do not cause an error * Generate v8.min.json
Commits on Oct 25, 2016
Commits on Nov 2, 2016
Commits on Nov 3, 2016
Commits on Nov 4, 2016
Commits on Nov 5, 2016
Commits on Nov 7, 2016
Commits on Nov 16, 2016
-
Remove/re-add layers when source-related properties change (#571)
* Remove/re-add layers when source-related properties change Two cases: - Fix #570 - remove/re-add layer when `source`, `source-layer`, or `type` properties are changed. - Remove all dependent layers before removing a source; if the source is being removed and re-added, then the corresponding layers are also added again afterward. (See #3621 (comment)) * Add explainer comment * Fix lint * Slightly better readability * One more comment
-
Add declass module to preprocess a style's paint classes (#573)
* Add declass module * Fix lint * Add tests confirming that input isn't mutated * Strip paint.CLASS definitions * Dedupe extend()
Commits on Nov 17, 2016
-
* Deprecate 'paint.*' * Copy v8.json => v9.json * Update API docs * Update narrative docs with deprecation of paint classes * Remove paint.* from v9 * Fix duplicate name * Add migrations/v9 * Tweak wording in deprecation note * Remove v9.json * Address review comments
Commits on Nov 21, 2016
Commits on Nov 29, 2016
-
Don't rely on splitting on periods; explicitly disallow arbitrary key…
…s in transitions (#559) * Don't rely on splitting on periods; explicitly disallow arbitrary keys only in transitions * Fix some uncaught errors with light validation * Disallow arbitrary keys in light transition validator * There are no functions in "light" * Stricter on functions * Remove TODO * Flip: from 'disallowArbitrary' (so, allowed by default) to 'allowArbitrary' (so, disallowed by default) * allowArbitrary -> allowArbitraryKeys * Define a clear order of operations for object element validation, remove "allowArbitraryKeys" option (#580) * Define a clear order of operations for object element validation, remove "allowArbitraryKeys" option * Rename "validate" to "validateSpec"
-
Add sdk-support property for layer types (#585)
All layers are supported since the first v8 compatible SDK release, with the exception of fill-extrusions, which is first supported in GL JS 0.27
-
Add support for circle-stroke-* properties (#579)
* Add support for circle-stroke-* properties * Update v8.json with PR feedback
Commits on Nov 30, 2016
-
-
-
-
Fix validation errors thrown when using a function for light intensity (
#598) * Fix validation errors thrown when using a function for light intensity * Fix lint errors * Fix validation errors thrown by "undefined" light objects
Commits on Dec 1, 2016
-
Add sdk-support for light properties (#605)
Only supported by GL JS 0.27+
Commits on Dec 2, 2016
Commits on Dec 5, 2016
-
Prohibit explicit exponential functions for piecewise-constant style …
…properties Fixes #601
Commits on Dec 8, 2016
-
Validate ascending stop order for zoom-and-property functions
The additional output changes here are due to refactoring the validator such that string domain values more consistently result in deducing a categorical function type. Fixes #594
-
Commits on Dec 9, 2016
-
-
Remove "property-function" on properties whose DDS status is undecided
* `"property-function": true` means DDS is enabled and implemented in at least one SDK * `"property-function": false` means we've decided this property will not support DDS * Lack of a value means we haven't decided, or haven't implemented it yet Fixes #592
Commits on Dec 14, 2016
Commits on Dec 15, 2016
Commits on Dec 16, 2016
-
* Added binary search for interval function * Added binary search to exponential function * Adding profile to tests * Got rid of copypasta code * Added hash map for categorical function * fixed hash generation * Fixed profile to actually generate string categories * Fixed variable re-declare that caused test to fail * Fixed potential bug that would allow categories like 'toString' to resolve even if they were not in the provided array
-
Fix infinte loop when referenced property is undefined (#33)
* Move "profile.js" into root directory Working with this repository is most convenient if all files in the “test” directory work with “tap.” * Avoid infinite loops for missing properties, add more tests * Uncomment test * Restore "missing property" behaviour
Commits on Dec 20, 2016
Commits on Dec 21, 2016
Commits on Dec 22, 2016
Commits on Dec 23, 2016
Commits on Dec 24, 2016
Commits on Dec 28, 2016
Commits on Jan 2, 2017
-
Indicate macOS SDK support (#641)
* Indicate macOS SDK support Added macOS SDK support information alongside the existing iOS SDK support information. Clarified that, with respect to the iOS and macOS SDKs, this document is intended as a file format reference for style authors rather than a runtime styling reference. * macOS SDK v0.2.1 * Removed link to iOS SDK API reference We’ll add the link back in as soon as iOS SDK v3.4.0 and macOS SDK v0.3.0 are officially released.
Commits on Jan 20, 2017
Commits on Jan 23, 2017
Commits on Jan 24, 2017
Commits on Jan 25, 2017
Commits on Jan 26, 2017
Commits on Jan 27, 2017
Commits on Jan 30, 2017
-
Remove support for implicitly-categorical functions
This turned out to add significant complexity to the gl-native implementation, and never took effect in gl-js due to a bug (#3717). Removing it due to the complexity it would add to gl-native and other implementations, and the following additional rationales: * As a general principle: explicit is better than implicit. * Most users will not be constructing functions by hand anyway. For those that do: * Requiring `"type": "categorical"` is not an undue burden, especially when coupled with a hinting mechanism in the validator as implemented here. * Implicitly supplying `"type": "categorical"` for string domain values introduces a potentially surprising difference between `"stops": [["1", 1], ["2", 2]]` and `"stops": [[1, 1], [2, 2]]`.