e28a3769a7
refs: https://github.com/TryGhost/Toolbox/issues/105 The idea here is to ensure we're at least warning on bad migrations patterns. If a pattern is already in use in an existing migration, we can use `eslint-disable-next-line no-restricted-syntax` to override it. For new migrations which still need these features this step will force the user to think about the performance of the construct they are using
112 lines
4.2 KiB
JavaScript
112 lines
4.2 KiB
JavaScript
const path = require('path');
|
|
|
|
module.exports = {
|
|
env: {
|
|
es6: true,
|
|
node: true
|
|
},
|
|
plugins: ['ghost'],
|
|
extends: [
|
|
'plugin:ghost/node'
|
|
],
|
|
rules: {
|
|
// @TODO: remove this rule once it's turned into "error" in the base plugin
|
|
'no-shadow': 'error',
|
|
'no-var': 'error',
|
|
'one-var': ['error', 'never']
|
|
},
|
|
overrides: [
|
|
{
|
|
files: 'core/server/api/canary/*',
|
|
rules: {
|
|
'ghost/ghost-custom/max-api-complexity': 'error'
|
|
}
|
|
},
|
|
{
|
|
files: 'core/server/data/migrations/versions/**',
|
|
excludedFiles: [
|
|
'core/server/data/migrations/versions/1.*/*',
|
|
'core/server/data/migrations/versions/2.*/*',
|
|
'core/server/data/migrations/versions/3.*/*'
|
|
]
|
|
},
|
|
{
|
|
files: 'core/server/data/migrations/versions/**',
|
|
rules: {
|
|
'no-restricted-syntax': ['warn', {
|
|
selector: 'ForStatement',
|
|
message: 'For statements can perform badly in migrations'
|
|
}, {
|
|
selector: 'WhileStatement',
|
|
message: 'While statements can perform badly in migrations'
|
|
}, {
|
|
selector: 'CallExpression[callee.property.name=\'forEach\']',
|
|
message: 'Loop constructs like forEach can perform badly in migrations'
|
|
}, {
|
|
selector: 'CallExpression[callee.object.name=\'_\'][callee.property.name=\'each\']',
|
|
message: 'Loop constructs like _.each can perform badly in migrations'
|
|
}, {
|
|
selector: 'ForStatement ReturnStatement',
|
|
message: 'Invalid use of a return statement within for-loop in a migration'
|
|
}, {
|
|
selector: 'CallExpression[callee.property.name=/join|innerJoin|leftJoin/] CallExpression[callee.property.name=/join|innerJoin|leftJoin/] CallExpression[callee.name=\'knex\']',
|
|
message: 'Use of multiple join statements in a single knex block'
|
|
}]
|
|
}
|
|
},
|
|
{
|
|
files: 'core/shared/**',
|
|
rules: {
|
|
'ghost/node/no-restricted-require': ['error', [
|
|
{
|
|
name: path.resolve(__dirname, 'core/server/**'),
|
|
message: 'Invalid require of core/server from core/shared.'
|
|
},
|
|
{
|
|
name: path.resolve(__dirname, 'core/frontend/**'),
|
|
message: 'Invalid require of core/frontend from core/shared.'
|
|
}
|
|
]]
|
|
}
|
|
},
|
|
{
|
|
files: 'core/server/api/**/utils/validators/**/index.js',
|
|
rules: {
|
|
'max-lines': ['off']
|
|
}
|
|
},
|
|
/**
|
|
* @TODO: enable these soon
|
|
*/
|
|
{
|
|
files: 'core/frontend/**',
|
|
rules: {
|
|
'ghost/node/no-restricted-require': ['off', [
|
|
// If we make the frontend entirely independent, these have to be solved too
|
|
// {
|
|
// name: path.resolve(__dirname, 'core/shared/**'),
|
|
// message: 'Invalid require of core/shared from core/frontend.'
|
|
// },
|
|
// These are critical refactoring issues that we need to tackle ASAP
|
|
{
|
|
name: [path.resolve(__dirname, 'core/server/**')],
|
|
message: 'Invalid require of core/server from core/frontend.'
|
|
}
|
|
]]
|
|
}
|
|
},
|
|
{
|
|
files: 'core/server/**',
|
|
rules: {
|
|
'ghost/node/no-restricted-require': ['warn', [
|
|
{
|
|
// Throw an error for all requires of the frontend, _except_ the url service which will be moved soon
|
|
name: [path.resolve(__dirname, 'core/frontend/**')],
|
|
message: 'Invalid require of core/frontend from core/server.'
|
|
}
|
|
]]
|
|
}
|
|
}
|
|
]
|
|
};
|