Customizing Profile

You can customize every profile by adding/editing one of the following files.

tables.json

{
  "tableName": {
    "fields": ["field1", "field2"]
  },
  "tableName2": null
}

Linter behaves as follows:

1. If table name is not configured (tableName3) - not present in the list, changes are ignored
2. If table name is configured (tableName2) - present in the list, but value is null, changes are marked for manual review
3. If table name is configured (tableName) - present in the list, containing configured fields, changes are linted

Currently the only table marked for manual review by default is wf_workflow. You can change existing tables or add new ones by editing tables.json in the profile folder.

resources.json

By creating resources.json in your profile, you can extend some details of your report.

Adding custom Report Overview - Resources links

{
  "overview-resources": [
    {
      "label": "Google",
      "link": "http://www.google.com"
    },
    {
      "label": "Example domain",
      "link": "http://www.example.com"
    },
  ]
}

eslint.json

Properties to configure ESLint object are the same as for the ESLint class

By default, Linter (if not configured otherwise) should first check for .eslintrc file in the folder where the command is executed at and then continuing up the folders until reaching user home directory.

To configure the NOW ESLint to use a specific ESLint configuration you can add overrideConfig property to it as such

{
  "overrideConfig": {
    "no-console": 1,
    "no-undef": 0
  },
}

To configure the NOW ESLint to use a specific ESLint configuration file you can add overrideConfigFile property to it

{
  "overrideConfigFile": "/users/sample-user/.eslintrc"
}

If you are using ESLint plugins, you will need to point linter to their installation folder via

{
  "resolvePluginsRelativeTo": "/users/sample-user/node_modules/"
}