IGVF-DACC / igvf-ui / #964

100%

main: 100%

push

IGVF-360 Fix API error message (#93)

IGVF-318-api-error

* You have to return the promise from API route functions or you’ll get the error message in the igvf-ui console described in IGVF-318. I also no longer request the access_key collection, as it’s private unless signed in. This removes a 400 error on every page load. We don’t create access keys through the same mechanism that we create other objects anyway.
* Use a dynamic route for mapprofile to make the request syntax easier, i.e. /api/mapprofile/<profile> instead of /api/mapprofile/?query=<profile>. I hadn’t realized you could have dynamic routes in /api when I wrote mapprofile the first time.
* Remove a stray console.log.

429 of 429 branches covered (100.0%)

Branch coverage included in aggregate %.

974 of 974 relevant lines covered (100.0%)

20.31 hits per line