Add API Reference and Guides for TypeScript in docs#2266
Add API Reference and Guides for TypeScript in docs#2266meganelacheny merged 20 commits intomainfrom
Conversation
Created new markdown files for API Reference and Guides under TypeScript development. Updated sidebar configuration to include these new sections and added corresponding links and placeholders.
This guide covers prerequisites, type imports, and usage examples for working with Strapi documents and components using TypeScript. It includes detailed sections on generic and known entities, advanced use-cases, and type argument inference to enhance type safety and development efficiency.
Updated the tags in the TypeScript development documentation to include 'api reference' and 'guides' for better categorization and easier navigation. This helps users find relevant information more efficiently.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pwizla
left a comment
There was a problem hiding this comment.
Thank you, JS! Super useful changes.
I left lots of purely technical writing-oriented comments.
Happy to discuss things with you if you want, or just apply most of them, depending on what you prefer 🤗
docusaurus/docs/dev-docs/typescript/development/guides/documents-and-entries.md
Outdated
Show resolved
Hide resolved
docusaurus/docs/dev-docs/typescript/development/guides/documents-and-entries.md
Show resolved
Hide resolved
docusaurus/docs/dev-docs/typescript/development/guides/documents-and-entries.md
Outdated
Show resolved
Hide resolved
docusaurus/docs/dev-docs/typescript/development/guides/documents-and-entries.md
Outdated
Show resolved
Hide resolved
docusaurus/docs/dev-docs/typescript/development/guides/documents-and-entries.md
Show resolved
Hide resolved
| - reference | ||
| --- | ||
|
|
||
| # API Reference |
There was a problem hiding this comment.
Until this page has some more content, I'd suggest we don't link to it from the sidebar and the TypeScript intro. page.
If you want to inform users that an API reference is in the works, I'd suggest you use the special :::strapi callout in the TypeScript development intro. page.
See my comment in the TypeScript development file :)
There was a problem hiding this comment.
Sorry, just taking over here while @Convly is off and don't fully understand what we would need to change. Could you update it the way you think would work best?
docusaurus/docs/dev-docs/typescript/development/guides/documents-and-entries.md
Show resolved
Hide resolved
…ts-and-entries.md
…ts-and-entries.md
…ts-and-entries.md
…ts-and-entries.md
…ts-and-entries.md
…ts-and-entries.md
…ts-and-entries.md
…ts-and-entries.md
…ts-and-entries.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
…ts-and-entries.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
…ts-and-entries.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
innerdvations
left a comment
There was a problem hiding this comment.
Looks good so far, just had some of the same comments as Piwi had
What does it do?
Add the first version for the first typescript guide in the documentation
Why is it needed?
Part of our effort to ease the adoption of TypeScript in Strapi