fix: support models with IDs starting with a number

[angeloashmore]

Types of changes

• [ ] Chore (a non-breaking change which is related to package maintenance)
• [x] Bug fix (a non-breaking change which fixes an issue)
• [ ] New feature (a non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

This PR add support for models with IDs that start with a number.

For example, a Custom Type with an API ID of 404_page or a Shared Slice with an API ID of 2ColumnText is now supported.

Before this PR, the code generator generated invalid code by creating types with names starting with a number. This is invalid TypeScript syntax, similar to starting JavaScript variables with a number.

As of this PR, types starting with a number are prefixed with an underscore (_).

• Old: 404Page (invalid, throws TypeScript syntax error)
• New: _404Page

Note: We recommend not starting model IDs with a number.

Using model IDs starting with a number introduces subtle bugs, such as the one described in this issue.

Find alternative ID names if possible. For example, 404Page could be NotFoundPage.

Fixes: #29

Checklist:

• [x] My change requires an update to the official documentation.
• [x] All TSDoc comments are up-to-date and new ones have been added where necessary.
• [x] All new and existing tests are passing.

🦒

[github-actions[bot]]

size-limit report 📦

Path	Size
dist/index.js	1.07 MB (+0.01% 🔺)
dist/index.cjs	1.08 MB (+0.01% 🔺)