Skip to content
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 type-generation error #68

Open
domihagen opened this issue Jul 5, 2023 · 4 comments
Open

Typescript type-generation error #68

domihagen opened this issue Jul 5, 2023 · 4 comments
Labels
type:bug This issue reports a buggy (incorrect) behavior.

Comments

@domihagen
Copy link

Hello together,

i am new to Strapi and want to use this great Plugin. But it seems like there is an issue.
When i am running the strapi command strapi ts:generate-types it throws this error:

[INFO]  [2023-07-05T07:58:37.567Z] (Typegen) Starting the type generation process
[INFO]  [2023-07-05T07:58:37.567Z] (Typegen) Generating types for contentTypes
[ERROR] [2023-07-05T07:58:37.573Z] (Typegen) Failed to generate types for contentTypes: Debug Failure. Unhandled SyntaxKind: Unknown.. Exiting
[INFO]  [2023-07-05T07:58:37.573Z] (Typegen) The task errored with 0 warning(s) and 1 error(s) in 0.006s.

When i remove the field that uses the CustomField with CKEditor in src/api/[collection]/content-types/[collection]/schema.json, the generation works.

@domihagen
Copy link
Author

Update

After deleting all the Collection-Types and creating them new it works...

I don´t know if you still want to check it or not. So i will keep the Issue open, but i am fine when you just close it.

@Witoso
Copy link
Member

Witoso commented Jul 6, 2023

@domihagen thanks for letting us know! I will keep this open to record the bug for future bug fixing.

@Witoso Witoso added the type:bug This issue reports a buggy (incorrect) behavior. label Jul 6, 2023
@kiscdbc
Copy link

kiscdbc commented Jun 19, 2024

Any updates on this one? We get the same error when using CKEditor as custom field. Removing the field fixes it, but we would rather keep it.

@blazingh
Copy link

i had this problem. after connecting to a new db it has been resolved.
i was deleting fields manually. i guess it is mandatory to only update fields from the content-type manager.
stupid mistake from me 🙃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug This issue reports a buggy (incorrect) behavior.
Projects
None yet
Development

No branches or pull requests

4 participants