Release notes

A log of core changes affecting API usage.

The Woosmap product team regularly updates the API with new features, bug fixes, and performance improvements. You can indicate which version of the API to load within your application by specifying it in the Woosmap Locator API bootstrap request.

This changelog lists releases by date and version number, along with associated changes.

[v1.4.17] - 2020-11-02

  • Remove Baidu autocomplete restriction to city as it does not work anymore.

[v1.4.16] - 2020-06-01

  • Use appendChild instead of append in maps loader.
  • IE11 does not supports append method.

[v1.3.11] - 2020-06-01

  • Use appendChild instead of append in maps loader.
  • IE11 does not supports append method.

[v1.4.15] - 2020-04-10

  • Use the up to date google maps loading script.

[v1.3.10] - 2020-04-10

  • Use the up to date google maps loading script.

[v1.4.14] - 2020-03-26

  • Avoids overwritting woosmap global if already present. (for example when localities was loaded.)

[v1.4.13] - 2020-03-03

  • Fixes a crash when setting position to null on BaseViews.

[v1.4.11] - 2020-01-24

  • Fixes a crash when window.$ is not jQuery.

[v1.4.10] - 2019-08-06

  • Remove usage of Promise#finally as we may encounter savage polyfills that overwrite ours in client sites.

[v1.4.7] - 2019-06-05

  • Fixes getDirectionsLink

[v1.4.4-0] - 2019-05-27

  • Fixes PlacesSearchsource issue, was returning {geometry: {location: {lat, lng}}} but the previous version was returning {location: {lat, lng}}. We now return both.
  • Fixes documentations issues (objects not marked private).

[v1.4.3] - 2019-05-22

  • Adds support for baidu directions and baidu autocomplete.
  • Fixes promises polyfill to properly support IE 11.
  • Fixes fitbounds method for badiu.

[v1.4.3-1] - 2019-04-24

  • Fixes fitbounds method for badiu.

[v1.4.3-0] - 2019-04-15

  • Adds support for baidu directions and baidu autocomplete.
  • Fixes promises polyfill to properly support IE 11.

[v1.3.9] - 2018-10-16

  • Sets the TableView#details mvc property with place details upon selection.
  • Adds sessionToken support to placesSearchSource.
  • Adds errorCallback to geocoder options.

[v1.4.0] - 2018-10-16

  • Sets the TableView#details mvc property with place details upon selection.

[v1.4.0-5] - 2018-10-02

  • Sets the TableView#details mvc property with place details upon selection.
  • Adds sessionToken support to placesSearchSource.
  • Adds errorCallback to geocoder options.

[v1.3.8] - 2018-08-09

Fixes

  • Replaces a rogue let instruction with var

[v1.4.0-3] - 2018-06-12

Fixes

  • Transforms Styler Size literals into google.maps.Size instances (the literals do not work in google maps 3.33)

[v1.4.0-2] - 2018-06-06

Fixes

  • Updates deployer dependencies, clear package-lock.json when switching branch.

[v1.4.0-1] - 2018-05-30

Features

  • Adds Baidu support.
  • jQuery is not required map display.
  • Adds maps package to encapsulate Baidu and Google.

  • Sets the TableView#details mvc property with place details upon selection. Query helpers (and, or) supported array with lengths >= 2.

    This caused problem when generating queries from for example checkboxes where only one could be checked.

    This would fail using sdk 1.3 when only one item is checked

    JavaScript
             let fields = collectFieldsFromCheckBoxes();
 let query = q.and(fields.map(t => q.F('type', t));

    When using an array with one element the enclosing q.and is omitted from the final query.

    JavaScript
             let query = q.and([q.F('type', 'a_type')]);
 let shorterQuery = q.F('type', 'a_type');

 query.toString() == shorterQuery.toString();
 // should equal 'type:"a_type"'

    It also support the omition of the array.

    The following query can now be simplified:

    JavaScript
             q.and([q.F('type', 'type1'), q.F('type', 'type2')]);
 // we can omit the array to be more concise.
 q.and(q.F('type', 'type1'), q.F('type', 'type2'));

[v1.3.7] - 2018-05-30

  • Transforms Styler Size literals into google.maps.Size instances (the literals do not work in google maps 3.33)

[v1.3.6] - 2017-09-11

  • Handle OriginDestinationInput origin & destination input states more gracefully
  • Fixes double search leads to search the “input label” (My Location).

[v1.3.5] - 2017-09-01

  • Fixes a crash in tileddataoverlay due to undefined bounds preventing initialization of the tiled image layer.

[v1.3.4] - 2017-07-05

  • Fix loading InfoBox on when woosmap.ui is undefined.

[v1.3.3] - 2017-06-28

  • Do not use woosmap.loadGoogleSubclasses function in initialize, woosmap object may not contain loadGoogleSubClasses function

[v1.3.2] - 2017-06-02

  • v1.3.2

[v1.3.2-0] - 2017-06-01

  • Returns the store_id in the mouseout event instead of undefined.
  • Debounces the event handler when an XHR must be made to get the Asset.
  • Adds asset cache to avoid fetching it twice on mouseover and mouseout.
  • Fixes removeListener that was not removing source listener.

[v1.3.1] - 2017-03-24

  • Fixes ReferenceError: event is not defined exception, that was problematic on Firefox. (reported by @pierrewgs)

[v1.3.0] - 2017-03-14

[v1.3.0-4] - 2017-03-13

  • Adds addListener & removeListener methods to woosmap.BaseView. This allows registering events for the event view independently of the event source (TiledImageLayer, DefaultRenderer, MarkersRenderer or a custom renderer).

[v1.3.0-3] - 2017-02-28

  • Removes data collection
  • Adds support for region parameter in MapsLoaderOptions
  • Adds support for version parameter in MapsLoaderOptions
  • Adds bounds and count support towoosmap.DataSource

[v1.3.0-2] - 2016-11-02

  • markers parameter in woosmap.View constructor may also be a BaseViewOptions object.
  • View(map:google.maps.Map, markersOrOptions?:String|Array.<DeprecatedStyleRule>|BaseViewOptions, zoomLevel?:Number)
  • markersOrOptions: String|Array.<DeprecatedStyleRule> is deprecated.
  • zoomLevel is deprecated, because it’s included in BaseViewOptions.

[v1.3.0-1] - 2016-10-11

Count map loads on baseview init.

[v1.3.0-0] - 2016-09-28

Features

  • Adds eventListeners option to renderers constructor allows registering handlers for named events on markers.
javascript
        var renderer = new woosmap.layers.renderers.DefaultRenderer({
    styler: new woosmap.style.Styler(),
    eventListeners: {
        'mouseover': function(store) {
            console.log('over ' + store.properties.store_id);
        },
        'mouseout': function(store) {
            console.log('out ' + store.properties.store_id);
        }
    }
}

Works with MarkersRenderer.

  • Adds woosmap.query namespace to handle new style queries. (more information here)
  • Adds woosmap.search.SearchParameters query property that allows passing raw string queries.
javascript
            var q = woosmap.query;

    console.log(q.and([q.or([q.F('tag', 'tag1'), q.F('tag', 'tag2')]), q.F('type', 'awesome type')]));
    // should return
    // ((tag:"tag1" OR tag:"tag2") AND type:"awesome type")
Deprecation notice
Deprecated objects
  • woosmap.search.SearchQuery
woosmap.TiledView
  • setSearchQuery(searchQuery:SearchQuery)
  • setPolylineFilter(polylineFilter:PolylineFilter) are replaced by setSearchParameters(searchParameters)
  • searchQuery & polylineFilter from TiledViewOptions, superseeded by searchParameters
woosmap.layers.TiledDataOverlay
  • setSearchQuery(searchQuery:SearchQuery)
  • setPolylineFilter(polylineFilter:PolylineFilter)

are replaced by setSearchParameters(searchParameters)

  • searchQuery & polylineFilter from TiledOverlayOptions, superseeded by searchParameters
woosmap.layers.renderers.DefaultRenderer
  • setClick(callback:Function)

superseeded by addEventListener(event:String, listener:Function)`

woosmap.layers.TiledImageLayer deprecated methods
  • setSearchQuery(searchQuery:SearchQuery)
  • setPolylineFilter(polylineFilter:PolylineFilter)

are replaced by setSearchParameters(searchParameters)

woosmap.search.SearchParameters
  • searchQuery property, you should use query property instead.
  • SearchParametersOptions searchTextOptions should use query option.
Deprecated before 1.3 cycle

Theese methods or option were deprecated before 1.3 but due to the lack of public information about their future removal this will be probably postponed to the 1.4 cycle.

In any case you should avoid using deprecated methods/options.

woosmap.DataSource
  • getStoresBySearchQuery(query:String, callback:Function)
  • searchStores(searchQuery:SearchQuery, callback:Function)
  • searchNearbyStores(searchQuery:SearchQuery, lat:Number, lng:Number, callback:Function, maxStores:Number, maxDistanceFromUser:Number)

are superseeded by searchStoresByParameters(searchParameters:SearchParameters, callback:Function)

SearchParameterOptions
  • maxStores superseeded by page and storesByPage
Was this helpful?