fix(markdown): allow plugin with array type option

[maximepvrt]

🔗 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 current implementation of the markdown plugins 'rehype' and 'remark' transforme the option array into object. When providing an array, such as [{selector: 'ol', wrapper: 'p' }, {selector: 'ul', wrapper: 'p' }], it is transformed into an object with numeric keys instead of maintaining the original array structure.

content: {
        markdown: {
            rehypePlugins: {
                'rehype-wrap-all': [{selector: 'ol', wrapper: 'p' }, {selector: 'ul', wrapper: 'p' }]
            }
        }
    },

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt-content canceled.

Name	Link
🔨 Latest commit	1f8a289
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-content/deploys/64b652851da5440008362d86

[farnabaz]

Thanks for the PR @maximepvrt
Do you mind adding a simple test for it?

[maximepvrt]

@farnabaz What test would you like me to add? Adding a plugin with a configuration of type 'array' in this file: https://github.com/nuxt/content/blob/main/test/fixtures/basic/nuxt.config.ts ? (for example rehype-wrap-all ?)

[farnabaz]

Yes usingrehype-wrap-all would be fine.
If adding rehype-wrap-all in nuxt.config breaks other tests, feel free to duplicate fixtures/basic/server/api/parse.ts and add plugin directly there, and use new API for the test

[maximepvrt]

@farnabaz Ready to merge. Looks good to me. 🚀

[farnabaz]

Thanks ❤️