refactor!: spell extensions correctly

[harlan-zw]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The key is spelled incorrectly, as someone who is adding a custom transformer I'd prefer not to have misspelled keys in my code.

BREAKING CHANGE: custom transformers should rename key extentions to extensions

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

‼️ Deploy request for nuxt-content rejected.

Name	Link
🔨 Latest commit	4a68090

[Tahul]

I'll let @farnabaz double-check this one but this LGTM. 😄

I don't think a lot of people actually uses custom transformers in their own projects yet, so even if this adds a breaking change it is fine to me to push this ASAP.

Thank you so much @harlan-zw

[pi0]

Nice catch @harlan-zw. But are you going to release content v3 for it ?! It could be a soft fix with typo fallback until next semver-major.

[harlan-zw]

Nice catch @harlan-zw. But are you going to release content v3 for it ?! It could be a soft fix with typo fallback until next semver-major.

Thanks for the review @pi0, you're absolutey right. A soft fix would have been a better option. I'll avoid these type of PRs in the future 👍

[pi0]

No worries! Is current change released? If not we might have a chance to avoid breaking.