feat: defineIntegration

[florian-lefebvre]

Description (required)

• Replaces occurences of AstroIntegration by defineIntegration
• Add a section documenting usage of defineIntegration
• Updates Astro DB integration docs
• TODO: show how to use a custom type using z.custom<MyType>()

Related issues & labels (optional)

• Suggested label: add new content, minor release

For Astro version: 4.8. See astro PR #10892.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Apr 30, 2024 5:23pm

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
docs-i18n	⬜️ Ignored (Inspect)		Apr 30, 2024 5:23pm

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale	File	Note
en	guides/astro-db.mdx	Source changed, localizations will be marked as outdated.
en	recipes/making-toolbar-apps.mdx	Source changed, localizations will be marked as outdated.
en	reference/dev-toolbar-app-reference.mdx	Source changed, localizations will be marked as outdated.
en	reference/integrations-reference.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[sarah11918]

Just getting ahead of this a bit, not full review:

This says "helpers" (plural), but then only seems to define defineIntegration(). Also, since this is an API reference page, thinking about what's scannable in the TOC, I think it might make more sense to have the actual code options visible vs descriptive headings. (People may often be using these pages to look things up, and seeing the various helpers/arguments etc. in the TOC makes that very easy to do.)

Would a structure like this make sense?

## `defineIntegration()`
<p><Since v="4.8.0" /></p>

### `optionsSchema`
<p><Since v="4.8.0" /></p>

### `setup`
<p><Since v="4.8.0" /></p>

[florian-lefebvre]

I have been thinking about this and my thinking was that, since we have a new entrypoint (astro/integration), more things could be exported in the future. So I decided to create a section for all the things that may end up in there. Let me know what you think! But I don't think it's worth reviewing just yet because we need to go through all the rfc stages