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
Allow all parameters to be defined in the config file, allowing them to be dynamically defined, but still be overridden by the CLI.
Currently it looks like there are currently options that can only be passed through the CLI. For example, reporters appears to only take configuration from the CLI options.
Example use case
To be able to define reporters in the config, making use of javascript to help define values. Consider a lage.config.js like this where i've put reporter and grouped in the root as an example:
Overview
Allow all parameters to be defined in the config file, allowing them to be dynamically defined, but still be overridden by the CLI.
Currently it looks like there are currently options that can only be passed through the CLI. For example, reporters appears to only take configuration from the CLI options.
Example use case
To be able to define reporters in the config, making use of javascript to help define values. Consider a lage.config.js like this where i've put
reporter
andgrouped
in the root as an example:With the package.json like:
Then:
npm run lint
on my local I want to see the npmLog reporternpm run lint
on my Azure DevOps Pipeline ( or manually withCI=true npm run lint
) I should see output from the azureDevops reporternpm run lint -- --reporter=json
anywhere then I expect the report output to be in JSON formatThe text was updated successfully, but these errors were encountered: