sij/mapnik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated Api changes between v2.1 and v2.2 (markdown)

Dane Springmeyer 2013-05-31 13:36:29 -07:00
parent 9add18eaa0
commit 5123b42851
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Api-changes-between-v2.1-and-v2.2.md

@ -5,8 +5,8 @@
- Removed the `bind` option for datasources (#1654)
## Changed
- `<Filter>[attr] != ''</Filter>` now matches only empty strings. This syntax previously matched both empty strings and nulls but this behavior was unintended and buggy given that Mapnik has supported a `null` type since 2.0.0. If you wish to filter out all `attr` values that are not `empty strings` or `null` or `false boolean type` then you can do `<Filter>[attr]</Filter>` or `<Filter>[attr] != '' and [attr] != null and [attr] != false</Filter>`
- Proj4 init errors due to invalid `srs` values will now cause exceptions when a map is loaded from XML as well as when encountered during rendering. The latter will very unlikely happen now that validation is done at map loading time. Previously errors were not reported except at render time and only as warnings printed to stderr (#646)
- <strike>`<Filter>[attr] != ''</Filter>` now matches only empty strings. This syntax previously matched both empty strings and nulls but this behavior was unintended and buggy given that Mapnik has supported a `null` type since 2.0.0. If you wish to filter out all `attr` values that are not `empty strings` or `null` or `false boolean type` then you can do `<Filter>[attr]</Filter>` or `<Filter>[attr] != '' and [attr] != null and [attr] != false</Filter>`</strike> No longer the case for 2.2 release, due to backwards compatibility fix as per https://github.com/mapnik/mapnik/issues/1859
## Added
- Added Logging framework documentation synced with 2.2 status: https://github.com/mapnik/mapnik/wiki/Logging