New Documentation release: Strapi v4.2.2

[piwi]

Hello everyone!

This week’s deployment is all about improvements and additions:

• We explicitly described how to programmatically access a plugin configuration with the Server API for plugins.
• We better explained the difference between the Entity Service API and the Query Engine API and when to use them.
• We improved the REST API documentation structure and examples.
• We described new GraphQL configuration options.
• We mentioned the external Design System documentation for easier access while customizing the admin panel.
• We added instructions on how to enable/disable telemetry with the CLI.
• We added documentation for configuring react-refresh, which enables faster development of the admin panel.
• We added a FAQ entry about Strapi running in serverless environments.

Improvements with the help of the community

• Update of the Unit testing guide - Thank you to juliangra for this contribution!
• Improvement of Services customization - Thank you to AlexMNet for this contribution!

[b3nab]

Great job guys, thanks all for the hard work.

I’m curious about the stable release of Typescript implementation of strapi. Will it be available a documentation or a tool about converting current strapi v4 (in JS) to use and get advantages of TS?

[piwi]

Thanks for your kind words @b3nab.
If I’m not mistaken, fully converting an existing vanilla-JS project to TypeScript is outside of the scope of the initial stable TypeScript release. But we’ll have some kind of tooling, especially with a CLI command that will generate TypeScript typings based on model schemas.
This will be documented in the next documentation iterations, and you can track the progress on this pull request.

Is there anything else I can help you with?

[nicolas_chauviere]

thank you very much for your work!
We migrated our CMS to Strapi and we do not regret our choice.
Long life to Strapi !

[piwi]

Thank you very much for the kind words @nicolas_chauviere