Nikolay
Nikolay
@francoischalifour Hmmm, thanks. A quick demo showed that the issue was our code passing `max` property to the connected range widget. I don't know whether the `max` property should remain...
I guess it's fine. The issue in our project is specific to the project: in that project, the `max` property gets automatically generated on every mount (is based on `Date.now()`)...
If you think that's not a bug then we could close it.
Currently, our workaround is: ```js transformSearchStateForLocation (searchState) { // console.log('Search State:', searchState); // Fixes `max` start date being capped at `now + 240 days` // which results in it depending...
Maybe it was a bug. See if the latest version works. Your sandbox uses an older version.
> I cannot update it in a sandbox because of this I see. Well, I don't look into ES Modules import issues in non-standard cases, and this seems to be...
> From what I understand, I think this is an issue of Webpack. I feel Webpack caches the resolved path for a given import path and doesn't use the resolver...
@jmengelle why do you say it was accepted while it's been open for a year?