diff options
| author | xmo-odoo <xmo@odoo.com> | 2017-06-09 12:26:38 +0200 |
|---|---|---|
| committer | Christophe Simonis <chs@odoo.com> | 2017-06-09 16:52:31 +0200 |
| commit | c50745f1a1f04ce06696a5095b5ff7407e7dac60 (patch) | |
| tree | 3cb4e92806f79586f0ec0b2ce7316bb8e08eb90c /addons/web/static/src/js/views/basic/basic_model.js | |
| parent | c6b9b69f6a483e7ccebf0b823240b71a8f426fd3 (diff) | |
[FIX] base_geolocalize: geocode errors out on empty address
It's unclear whether that's a recent change or a long-standing issue,
however currently if geocode is called with an empty address string it
will reply with a 400 Bad Request, which gets raised as an exception and
forwarded to the user. That is not a great experience.
Shortcut the entire thing and just return None (= geolocation failed /
no geolocation) on trying to geolocate an empty address.
OPW-746686
backport of 74a89bcf5c656a0a64f2a699444d39739ff7f1d2
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_model.js')
0 files changed, 0 insertions, 0 deletions