Hey users of the Maps extension,
I'd like to get your input on making breaking changes in the Maps extension
[0]. With breaking changes I mean those that remove existing functionality
or those that change it in some way that they will behave differently or be
broken if you as a user do not take action to migrate.
Are there any features that you think are not worth the confusion they
cause? Are features you do like confusing to use, perhaps because of
something like badly named parameters? In either case, please write me, and
perhaps I'll add this to the list of things to be removed or changed.
These are the breaking changes already made for the 5.0 release, to give
you an idea:
* Removed geoservice parameters from the #display_map parser function
* Removed geoservice and allowcoordinates parameters from the #geocode
parser function
* Removed mappingservice and geoservice parameters from the #geodistance
parser function
* Removed mappingservice, geoservice and allowcoordinates params from the
#finddestination parser function
* Removed geoservice parameter from the SMW result formats
* Removed service parameter from the geocode API module
* Removed egMapsUserGeoOverrides setting
* Removed egMapsAvailableGeoServices setting
* Removed egMapsAllowCoordsGeocoding setting
* Removed support for the GeocoderUS geocoding service as it appears to
have shut down
Only the major releases of Maps (3.0, 4.0, 5.0, etc) contain breaking
changes. This is why I'm now looking for good candidates to put in the 5.0,
as after this release it won't be possible to make such changes for a year
or so.
Cheers
--
Jeroen De Dauw |
https://entropywins.wtf |
https://keybase.io/jeroendedauw
Software craftsmanship advocate | Developer at Wikimedia Germany
~=[,,_,,]:3