-
Notifications
You must be signed in to change notification settings - Fork 343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat: support .web-ext-config.js
in the current directory.
#2812
Comments
I don't understand the naming choice either; it was proposed in #730. We can support another config file by adding it to https://github.com/mozilla/web-ext/blob/3ff64882d0e46c2952cbd661541981d68cc0a03f/src/config.js#L151C28-L158 , plus unit tests. For relevant files to touch, see the PR where the feature was originally introduced: #1161. We should merge this change only at the next major version update, because the inclusion of a config file can potentially change the observed behavior. For example, a project could have a template |
@willdurand Let me know if this requires qa and what to check. |
@ioanarusiczki yes please. This is about making sure that we can use a config file named |
Inside add-ons folder I've added I hope that's expected, a bit confusing because here mentions a slash being used (not backslash) later edit I found the explanation, I'm working on Windows and slashed are probably on Linux and MacOS |
@ioanarusiczki |
Feat
about Automatic discovery of configuration files, I hope that support
.web-ext-config.js
in the current directory, instead ofweb-ext-config.js
.i dont undestand why the name of configuration files is different home dir and current dir. I don't think it's necessary
The text was updated successfully, but these errors were encountered: