Update the code example of <Code /> with transformers inapi-reference.mdx

[liruifengv]

Description (required)

• Update the code example of <Code /> with transformers

• <Code /> alone in the .astro file does not render correctly.

• I don't know if this is a bug, only update the docs to make sense for people that want quickrun.

  Before	After

Related issues & labels (optional)

• Closes #
• Suggested label:

[vercel]

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

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Jun 21, 2024 3:11am

[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	reference/api-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]

I'm not sure it's expected that the <Code /> component should need a wrapping <div> to style it!

Maybe we should first check to see whether this is a bug, or something about the implementation in withastro/astro#11197

Can @ematipico @bluwy or @braebo help us out here with the code sample we should document, and whether this behavior is expected?

[braebo]

That particular div in the example is indeed extraneous and unrelated to styling.

[sarah11918]

@liruifengv - You might have found a bug then! If you can reproduce for the team, can you please file an Astro issue?

I'll close this as a Docs PR since the intended behaviour is already documented.

[liruifengv]

@liruifengv - You might have found a bug then! If you can reproduce for the team, can you please file an Astro issue?

I'll close this as a Docs PR since the intended behaviour is already documented.

Ok. I will open a issue for core repo