Bryan Housel b48a7d1e1b Workround for status errors thrown by d3-xml ...

Because the done callback is expecting something that has a `status` property,
(like an XHR would), we need to extract the status out of the error message.
d3-xml includes status in the error message, but we can't access the response itself.

2019-04-26 22:23:08 -04:00

..

actions

Support straightening of points

2019-04-24 01:55:43 -04:00

behavior

Trying to avoid one-off validations when history changes will trigger it

2019-04-05 11:37:02 -04:00

core

When calling an errback from a Promise.catch, pass err.message

2019-04-25 21:58:36 -04:00

geo

Support straightening of points

2019-04-24 01:55:43 -04:00

modes

Merge branch 'master' into validation_and_change_perf

2019-04-10 14:22:20 -04:00

operations

Support straightening of points

2019-04-24 01:55:43 -04:00

osm

Merge branch 'master' into validation_and_change_perf

2019-04-10 14:22:20 -04:00

presets

Swap out d3-request, swap in d3-fetch

2019-04-24 16:25:25 -04:00

renderer

When calling an errback from a Promise.catch, pass err.message

2019-04-25 21:58:36 -04:00

services

Workround for status errors thrown by d3-xml

2019-04-26 22:23:08 -04:00

svg

Swap out d3-request, swap in d3-fetch

2019-04-24 16:25:25 -04:00

ui

When calling an errback from a Promise.catch, pass err.message

2019-04-25 21:58:36 -04:00

util

Consolidate idle functions into idle.js, defer validation after merge

2019-04-12 10:49:21 -04:00

validations

Add validation warning for unsquare buildings

2019-04-23 15:50:52 -07:00

id.js

Add abortcontroller-polyfill to support abortable fetch calls

2019-04-24 16:24:13 -04:00

index.js

Don't export coreValidator here, as it's already exported by core *

2019-03-30 09:58:42 -04:00