@bud-tools/eslint-plugin-bt-plugin v0.9.0

eslint-plugin-bt-plugin

Helpful eslint rules for bt plugins.

Use these rules in a bt plugin

yarn add --dev eslint-plugin-bt-plugin

Then, in your plugin's .eslintrc.js, add "plugin:bt-plugin/recommended" to your extends property.

example:

module.exports = {
  extends: ['@bud-tools/eslint-config-budtools-typescript', 'plugin:@bud-tools/bt-plugin/recommended'],
};

To override how an individual rules behaves, add the plugin name and change the its rules value.

plugins: ['bt-plugin'],
rules: {
  'bt-plugin/no-hardcoded-messages': 'error'
}

Use these rules to migrate a plugin based on btdxCommand to use btCommand

These eslint rules are experimental and cause significant code changes. Please use with caution and test changes thoroughly

yarn add @bud-tools/bt-plugins-core
yarn add --dev @bud-tools/eslint-plugin-bt-plugin

migration includes all of the recommended rules, so you don't have to include both

module.exports = {
  extends: ['@bud-tools/eslint-config-budtools-typescript', 'plugin:@bud-tools/bt-plugin/migration'],
};

Rules

💼 Configurations enabled in.\ ⚠️ Configurations set to warn in.\ 📚 Set in the library configuration.\ ✈️ Set in the migration configuration.\ ✅ Set in the recommended configuration.\ 🔧 Automatically fixable by the --fix CLI option.\ 💡 Manually fixable by editor suggestions.