Jonas Pauthier

Actually let me take back what I think in my previous comment. It worked for a few days but stopped working again. Thanks @folke your solution worked for me as...

I'm pretty busy as well on my side. I ported the theme to Lua but I don't have the time to work on the light theme for now.

@hasanify Can you submit a repro repo with the large document you're sending, please? This way we can reproduce the problem on our end and find the bug if there...

I think if you use `anySchema.warning()` the warning will always be thrown so you don't have the conditional behaviour you're looking for. Have you tried using a custom validation for...

Sure, I understand @Haroenv. Having dynamic min/max would be best but what about disabling the "go" button? If we just add the behaviour it'd be a breaking change obviously but...

Thanks for sharing the link @Haroenv that was informative. I know it might not be the best in terms of UX to disable the button when the component is in...

Ok no problem. I'll keep the issue open then. Thank you for your help.

When using `filter_by` for a `IN` operator kind of query, e.g `filter_by=category:=['cat1', 'cat2', ...]`, is there a limit on the number of values that you can search in? I tested...

I retested with existing values and not dummy generated ones. I didn't face any issues and they all seemed to be accounted for.

Alright, thanks for the info. I'll see if we can retest it with the latest version.