You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we standardize on oxlint.json or similar as the default config file that's supported? There's been a few times in testing where I add a config file and forget to add it to the CLI and then get confused for a while trying to figure out why my configuration isn't being respected.
This would make onboarding easier.
Or at the end of running, perhaps spit out the name of the config file, or a warning if no config was provided/detected?
The text was updated successfully, but these errors were encountered:
Can we standardize on
oxlint.json
or similar as the default config file that's supported? There's been a few times in testing where I add a config file and forget to add it to the CLI and then get confused for a while trying to figure out why my configuration isn't being respected.This would make onboarding easier.
Or at the end of running, perhaps spit out the name of the config file, or a warning if no config was provided/detected?
The text was updated successfully, but these errors were encountered: