-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
💡: cspell-define-config
package: add to docs
#5358
Comments
Than you for the suggestion. I would prefer a PR to add a new endpoint to import { defineConfig } from 'cspell';
export default defineConfig({
version: "0.2",
ignorePaths: ["node_modules/**", "**/vendor/**", "temp/**", "dist/**", "build/**"],
minWordLength: 4,
allowCompoundWords: true,
words: [],
ignoreWords: [],
import: [],
}); It is already possible to get the types from /**
* @param {import("cspell").CSpellSettings} cfg
* @returns {import("cspell").CSpellSettings}
*/
function defineConfig(cfg) {
return cfg;
}
export default defineConfig({
version: '0.2',
ignorePaths: ['node_modules/**', '**/vendor/**', 'temp/**', 'dist/**', 'build/**'],
minWordLength: 4,
allowCompoundWords: true,
words: [],
ignoreWords: [],
import: [],
}); But I can see how it might be useful to just have a function to use. |
I'm thinking about PRing it to
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Problem
No response
Solution
I've created and npm package named
cspell-define-config
to provide types forcspell.config.js
. It's nice to add it to the docs at https://cspell.org/configuration/Example
Alternatives
No response
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: