Releases: georust/tilejson
Releases · georust/tilejson
Release TileJSON v3 support, bounds, and center structs
Note that this GitHub release catches up to what has been release to crates.io
ATTENTION: This release contains many breaking changes. See README for usage examples.
v0.3.2 (2022-10-30)
- Add
Bounds::from
for[f64; 4]
,[f32; 4]
,[i32; 4]
- Add
Bounds::try_from
now also supports&[f64]
,&[f32]
,&[i32]
in addition toVec<f64>
v0.3.1 (2022-05-29)
- Add
Bounds::MAX
to create a maximum -180..180, -90..90 value. - Add
Bounds::MAX_TILED
to create a maximum allowed for vector tiles per spec. - Implement
Add
andAddAssign
onBounds
v0.3.0 (2022-05-25)
- Migrate to Rust 2021 edition
- update docs to match v3.0.0 spec
- add
fillzoom
field per v3.0.0 spec - add
Center
andBounds
structs instead of arrays- both support
FromStr
trait
- both support
- add
VectorLayer
struct and thevector_layer
field - Remove builder pattern because
TileJSON
is writable - Add
other
fields for any unknown fields in root and vector layers - Restructure instantiation:
- use
tilejson!{ source }
macro to createTileJSON
objects, with any number of the optionalfield: value
pairs. - use
set_missing_defaults()
to replace all missing values with their defaults (only if the spec defines it)
- use
- Remove
id
field because it is not supported by the spec
Relevant PRs
- Implement v3 by @nyurik in #12
- add Center and Bounds structs by @nyurik in #13
- Refactor instantiation, vector layers by @nyurik in #14
- Use tilejson! macro for instantiation, refactor by @nyurik in #16
- Add Bounds MAX, MAX_TILED, Add, AddAssign by @nyurik in #19
- Make
Bounds::try_from()
more generic by @nyurik in #18
New Contributors
Full Changelog: v0.2.4...v0.3.2
v0.2.4
What's Changed
- fix: use String instead of &'static str fpr tilejson field by @stepankuzmin in #7
Full Changelog: v0.2.3...v0.2.4
v0.2.3
What's Changed
- fix: skip serializing if Option is None by @stepankuzmin (h/t @jaspervercnocke) in #6
Full Changelog: v0.2.2...v0.2.3
v0.2.2
v0.2.2
- a7cffa8 feat: change type of bounds to f32 instead of i32 (#1) (h/t @jaspervercnocke)