David Amyot

This is a needed feature. If all the fields are empty, all should be disabled for the user besides the first one.

Personally, I would greatly appreciate for this pr to be merged since this is the only package I have left which creates this warning :) Thanks for the great work!

> Hi, Any update on this? I wish! @mrlaessig Any chances of this getting merged? Thanks :)

Would be very practical to allow for custom env files if possible. In our case, we have a **staging** environment for which we'd like to have a `.env.staging` but make...

> > Would be very practical to allow for custom env files if possible. In our case, we have a **staging** environment for which we'd like to have a `.env.staging`...

+1 Any param whose value has a closing parenthesis `)` will make it so that no params are passed altogether even if the other params are fine. ```jsx router.push({ pathname:...

Any chance of this being merged soon? Have to work with a fork otherwise. Thanks :)

@buncis Try with just `gem "whenever"` in your gemfile so that it's required to see the issue. Same issue for me here, `Rails 7.0.4.2` with `ruby 3.2.1 (2023-02-08 revision 31819e82c8)...

+1

Same issue as @FFGFlash mentioned. Performance is back, but now most strings offer tailwind intellisense when it shouldn't. Attached is a screenshot example of the intellisense with expo-router for defining...