The discussion revolves around resolving ESLint errors related to undefined ‘settings’ variables in ES6 files within a Discourse plugin. pfaffman is encountering multiple no-undef errors despite using settings, and seeks a way to convince ESLint that these variables are defined. david suggests the issue might stem from the shared lint-configs not properly handling the variables, referencing the config file here. merefield directs pfaffman to the lint-configs README for guidance. cvx proposes removing the .es6 file extension as a potential fix. pfaffman confirms that dropping the .es6 suffix resolves the errors, raising the question of whether a global rename of all .es6 files is advisable.
/home/runner/work/discourse-custom-homepage-for-groups/discourse-custom-homepage-for-groups/javascripts/discourse/initializers/custom-homepage-set.js.es6
Error: 13:11 error 'settings' is not defined no-undef
Error: 14:21 error 'settings' is not defined no-undef
Error: 19:20 error 'settings' is not defined no-undef
Error: 20:21 error 'settings' is not defined no-undef
Error: 25:36 error 'settings' is not defined no-undef
Error: 26:21 error 'settings' is not defined no-undef
Error: 32:40 error 'settings' is not defined no-undef
Error: 33:26 error 'settings' is not defined no-undef
Hm, maybe there’s an incompatibility between the newest eslint config and es6 files. Could you see if the errors persist after dropping the .es6 suffixes?