.codeclimate.yml

# This is a sample .codeclimate.yml configured for Engine analysis on Code
# Climate Platform. For an overview of the Code Climate Platform, see here:
# http://docs.codeclimate.com/article/300-the-codeclimate-platform

# Under the engines key, you can configure which engines will analyze your repo.
# Each key is an engine name. For each value, you need to specify enabled: true
# to enable the engine as well as any other engines-specific configuration.

# For more details, see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform

# For a list of all available engines, see here:
# http://docs.codeclimate.com/article/296-engines-available-engines

engines:
  phpcodesniffer:
    enabled: true
    config:
      standard: "Wordpress"
    checks:
      WordPress VIP RestrictedFunctions get_page_by_title_get_page_by_title:
        enabled: false
      WordPress VIP PostsPerPage posts_per_page_posts_per_page:
        enabled: false
      WordPress VIP RestrictedFunctions wp_remote_get_wp_remote_get:
        enabled: false
  fixme:
    enabled: false

# Engines can analyze files and report issues on them, but you can separately
# decide which files will receive ratings based on those issues. This is
# specified by path patterns under the ratings key.

# For more details see here:
# http://docs.codeclimate.com/article/289-configuring-your-repository-via-codeclimate-yml#platform

ratings:
  paths:
    - "**.php"
#   - app/**
#   - lib/**
#   - "**.rb"
#   - "**.go"

# You can globally exclude files from being analyzed by any engine using the
# exclude_paths key.

exclude_paths:
  - "bin/**/*"
  - "dist/**/*"
  - "tests/**/*"
  - "vendor/**/*"
  - "wordpress-svn/**/*"
  - "wp-tests/**/*"
  - "src/bower_components/**/*"
  - "src/admin/js/1/**/*"
  - "src/admin/js/flatpickr/**/*"
  - "src/admin/js/select2/**/*"
  - "src/timelinejs/**/*"
  - "src/js-client/**/*"
  - "src/js/**/*"
#- spec/**/*
#- vendor/**/*