i18n(es): Correction of missing imports for the function 'translatePath'

[fabriciodev26]

Imports should have been added so that the "translatePath" function can be used.

Description

I have corrected the lack of required imports for the 'translatePath' function. This ensures that the code can correctly access and use the 'translatePath' function, thus improving the integrity and functionality of the project.

[vercel]

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

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Jul 8, 2024 11:07am

[astrobot-houston]

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any broken links you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[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
es	recipes/i18n.mdx	Localization changed, will be marked as complete. 🔄️

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.

[TheOtterlord]

Thanks for the PR!

I like being more verbose here, although if we're adding the imports, we should also add the statement defining translatePath to complete the snippet, as it's not exported directly. I guess we could import the defaultLang as the value to pass to useTranslatedPath (it's only needed as it's a required typed param).

const translatePath = useTranslatedPath(defaultLang);

I've not made any code suggestions in GitHub because our translated pages source their content from the english versions, so any changes need to be made to the en version of this file. We accept the english version first, then translated versions as separate PRs.

[sarah11918]

Hi @fabriciodev26 - Just a reminder that if you'd like to contribute this change, it must be made to the /en/ version of the file! (not /es/)

Please let us know if you're interested in making that change! 🚀

[yanthomasdev]

Thanks @fabriciodev26, I'll block this PR from being merged till you make these changes in the English version of the page instead.

[delucis]

Thanks @fabriciodev26! I think this needs a small change.

made change to match English version

[sarah11918]

Thank you everyone! I've just gone ahead and committed the changes to match so this PR can be published and helping people!