fix(code-block): meta property

[farnabaz]

🔗 Linked issue

resolves #2059

❓ 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

📝 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	04aa05f
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-content/deploys/646b8892cc246c0008a20897

[nobkd]

Previous comment:

A problem is, that the meta regex has a fixed order for lang […] {…} meta
It is not replaced if we write lang {…} […] meta, even though L21-22 allow different ordering.

Also, if we want to use {…} or […] in the meta block, but not provide highlights or a filename, it will be matched (by L21-22).
Maybe, the user could provide an empty [] or {} block before the meta to prevent it from reading those parts in the meta.
Something like: lang [] meta=['not', 'a', 'filename'] would be possible then

---

In my opinion, we should also trim the lang property before checking if it is empty (adding it in L11)

lang = lang.trim()

Also return undefined (or an empty string '') for the meta if lang is empty (adding in L17)

{
  // ...
  meta: undefined
}

[nobkd]

Looks good to me.

But I don't know if it's good to return empty strings on empty filename, or if we should return undefined instead... 🤔

What do you think?

[nobkd]

This would be my change, if we don't want to return empty strings.