Closed JesJehle closed 1 year ago
The range filter now deactivates itself, if not all necessary base-data is available (ie. the min and max values). I will check the logic, I seem to have missed something...
Fixed the error in branch #73.
Vor height
changed passing value from value={height}
to
value={{
lower: height?.lower!,
upper: height?.upper!,
}}
for radius multiplied value by 100 🤕
Ok, as soon as I closed the inspector, the filter doesn't work anymore.
OK, I guess then there is something wrong with the component lifecycle as using the inspector and console.log stuff always slows the app down. I'll have a look
After initializing, the all range filters are deselected, most of the time.