-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
TypeScript support for config #346
Comments
Will do at some point. A workaround can be found in #215 but it’s not perfect as Sveltia CMS has added some new options. |
Actually we already have JSDoc type definitions. I’ll try to generate |
Type generation is working well locally. I’ll make sure all types are up-to-date according to the Decap CMS document. |
It turns out
|
Shipped v0.63.1 with TypeScript support. |
Just checked now. Works great, thank you for the quick fix:) |
Config can be given through a JSON/YAML file, and through
init({config: {backend: {name: "git-gateway"}, ...}})
as shown here.Right now, the
@sveltia/cms
is not typed at all, which is fair, given that Decap CMS and as such Sveltia CMS too, is probably mostly used through the JSON/YAML config.However, providing it through the init function has two major benefits:
Therefore I'm suggesting the typing of the package. Inspiration could be taken from here: https://github.com/decaporg/decap-cms/blob/main/packages/decap-cms-core/index.d.ts
The text was updated successfully, but these errors were encountered: