PB-2064: Fix search result test - #1546
Conversation
deb4d01 to
f17ffe2
Compare
12cd9a3 to
17cab68
Compare
There was a problem hiding this comment.
You shoud change all the forced void you used with something like
searchStore.setSearchQuery('', {}, dispatcher)
.catch((error) => {
log.error({
title: 'Some title',
messages: ['Error while searching', error]
})
})The ESLint/TS error that is raised there should then disappear (no need to .then everything, but you at least need to catch the errors of the promise you create)
2646456 to
fc77ba8
Compare
fc77ba8 to
5a1e0dd
Compare
…oiding re-injection
… better state consistency
ec82ae6 to
201b7ae
Compare
Fix proj4 not being registered in search API by externalizing peer dependencies (proj4, axios, ol) so they use the host application's instances instead of bundled copies.
Pass translations (kantone -> "Ct.", district -> "District") through the search API chain so location results display the correct origin prefix in the UI.
|
@pakb, it turns out that there is a change in the search API (translation) and a different proj4 instance in api and coordinate (no Swiss CRS). Also, for the mouseenter and mouseleave, I can't make |
|
strangely, the search result tests are running so long... |
|
@pakb, the tests pass locally, but I need to run them one by one. If I run all 3 tests together, my cypress cries and the test cann't be run because timeout |
Let's see if this improve the situation on the CI
pakb
left a comment
There was a problem hiding this comment.
splitting the last test fixed the file 🎉

Test link