Clayton lets you scan your app metadata and check that your code doesn't contain any code quality issue. The rules applied to your source code during the analysis are configurable (see Project Rules).

Supported file types

Clayton includes in its review the following file types.

  • Apex (.apxc, .apxt, .trigger, .cls, .apex)
  • Javascript (.js)
  • Lightning components (.cmp)
  • Visualforce files (.page, .component, .apexp)
  • Metadata files (.xml, .object, .workflow)

Reviewing branches

When performing a code reviews of a branch, Clayton retrieves the last revision for that branch, and performs a full scan of your code, selecting all supported file types found in the source code.

Pull requests

When performing a review of a pull request, Clayton works in incremental mode, only focusing on the files - among the support file types - that have been changed as part of the pull request. Files and lines that haven't been changed as part of a pull requests are ignored.

Ignoring files

Sometimes there are parts of your code that you don't actively intend to maintain. Clayton lets you ignore such files, so that they are never included in your scans, by adding them to the project ignore list. This is relevant, for example, in the following circumstances:

  • Unmanaged packages
  • Third party JavaScript libraries
  • Areas of the code that you are no actively maintaining

When a file in your source code matches a filename in the project ignore list, it's excluded from the analysis.

Did this answer your question?