- Add new worldview/class fixtures:
- add new fixtures
073
Class: _mbx_worldview "all", _mbx_class "sea" - add new fixtures
074
Class: _mbx_worldview "US,CN", _mbx_class "sea" - add new fixtures
075
Class: _mbx_worldview "US", _mbx_class "sea" - add new fixtures
076
Class: _mbx_worldview "US", _mbx_class not a string
- add new fixtures
- Add
create
method to module, allowing inline fixtures to be created for faster iteration in downstream libraries.
- Add new worldview fixtures:
- add new fixtures
064
Point features with added language & worldview properties prefixed with "_mbx_xxx". - add new fixtures
065
Worldviews: all legacy values - add new fixtures
066
Worldviews: all legacy and new values - add new fixtures
067
Worldviews: "all" values - add new fixtures
068
Worldviews: mixture of features - add new fixtures
069
Worldviews: _mbx_worldview is not a string - add new fixtures
070
Worldviews: _mbx_worldview and worldview properties in same feature with conflicting values - add new fixtures
071
Worldviews: all worldviews as separate features - add new fixtures
072
Worldviews: comma-separated list of non ISO 3166-1 alpha-2 codes
- add new fixtures
- Add new fixture
063
which has a set of features with different language values, which is helpful for testing internationalization functionality downstream #103 - Test on Node.js v16 + v14, remove testing for Node.js v8
- Add new fixture
062
which has a set of features with different property values, which is helpful for testing filtering functionality downstream #102 - Test on Node.js v10 + v8, remove testing for Node.js v4 + v6
- Use
Buffer.from()
instead ofBuffer()
- Remove mason_packages from NPM publish - remove .npmignore all together and use .gitignore
- Update fixture
011
to use a larger, less-likely-to-come-into-future-conflict number for the custom value type #99 - Add a new fixture
061
with with a linestring geometry that contains a ClosePath command #94
- Add two new fixtures used for layer compositing tests #97
- add broken geometry fixtures #86
- clipped square fixtures #87
- large MoveTo and LineTo command fixtures #88
- Update fixture
002
to include a set of tags. This makes it more "testable" since the ID does not exist. #85 - Mark fixture
009
as valid #64
- Fix fixture
011
to throw expected error per #82
- Add OSM QA tiles for more diverse real-world examples #76
- Update fixture 015 (duplicate layers) to include unique tags, which simplifies asserting on expected features #78
- Fix San Francisco real-world fixtures to z15 so we include buildings. Also reduces the number of fixtures dramatically to save on size. #72
Complete restructure of mvt-fixtures using pbf and protocol-buffers-schema, focused on maintainability and tools for quickly generating new fixtures. 🎉 Major improvements:
- All fixtures have their own source file (by ID) that contains information including a description, validity specs, and a JSON representation of the fixture used to generate a protocol buffer. All fixtures are described in FIXTURES.md
- Include a javascript API with
get
andeach
methods, described in API.md - Add real-world fixtures from mapbox-streets and mapbox-terrain tilesets. All real world fixtures are described in REAL-WORLD.md
- Add protoc scripts to dump raw text form of buffers to stdout for debugging
- Automated API and fixture documentation
- Fix some invalid fixtures #69
- gunzip and null encode all of the real-world fixtures, plus include some fixtures that are gzipped. #67
- Revert 3.0.0-beta3 removal of submodule, fix paths instead
- Vendorize vector-tile-spec repository so it packages with npm publishes #61
- Recreate all fixtures that previously existed in 2.x
- Add protoc scripts to dump raw text form of buffers to stdout for debugging
- Update generateBuffer to run specific versions of the Mapbox Vector Tile Specification, or custom proto files
- Generate with proto2 syntax by default instead of proto3 syntax to avoid situations where default values confusion
- Create source files for all fixtures in the src/ directory - these are node modules which include information about the fixture, including a description, validity specs, and a JSON representation of the fixture.
- Rely on
pbf
andprotocol-buffers-schema
modules to generate fixtures based on the Mapbox Vector Tile Specification, which is now a submodule to this repository. - All fixtures are generated into the fixtures/ directory programmatically using
npm run build
- Include a javascript API with
get
,create
, andeach
methods, described in API.md - Automatically generate fixture documentation from the source files, located in FIXTURES.md
- Rename project to
mvt-fixtures
- Break fixtures into
valid
andinvalid
directories - Match version with that of the Mapbox Vector Tile Specification (no longer true as of version 3.x)
- First official set of
.mvt
fixtures for usage within tests. All scripts used for create are currently within_reserve
so we can ponder how to use these in the future.
- first