Menu
White Clarke GroupLiquibase Linter
SetupRulesBlogGitHub
White Clarke GroupLiquibase Linter
  • Setup
  • Rules
  • Blog
  • GitHub
  • Setup
    • Install
    • Configure
    • Retrofitting
  • Rules
    • Using Rules
    • Custom Rules
      • Implementing a Custom Rule
    • Core Rules
      • create-column-no-define-primary-key
      • create-column-nullable-constraint
      • create-column-remarks
      • create-index-name
      • create-table-remarks
      • drop-not-null-require-column-data-type
      • file-name-no-spaces
      • file-not-included
      • foreign-key-name
      • has-comment
      • has-context
      • illegal-change-types
      • isolate-ddl-changes
      • modify-data-enforce-where
      • modify-data-starts-with-where
      • no-duplicate-includes
      • no-preconditions
      • no-schema-name
      • no-raw-sql
      • object-name
      • object-name-length
      • primary-key-name
      • schema-name
      • separate-ddl-context
      • table-name
      • table-name-length
      • unique-constraint-name
      • valid-context
Version: Next

has-context

Why?#

Usages of contexts vary a lot, but if you are using them heavily then you might want to make sure that all changeSets have a context, since omitting it will mean the changeSet is always run.

The has-context rule will fail if any changeSets don't have a populated context attirbute.

Options#

No extra options.

Previous
« has-comment
Next
illegal-change-types »
  • Why?
  • Options
White Clarke Group Logo
Copyright © 2021 White Clarke Group