fix: allow to override h1 to h6 through discovered components

[Xstoudi]

🔗 Linked issue

#1

❓ Type of change

• 🐞 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

dashCase is not what's needed there, we just want to replace _ with - as-is. Let me know if you'd prefer an other way to allow package users to override h2 node by loading h2.edge component. Without the change, dash casing load h2.edge as h-2, meaning it will never be used to replace ## title in markdown.

📝 Checklist

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

[thetutlage]

The issue is, what if the filename on the disk is saved as camelCase or PascalCase?

[Xstoudi]

Thanks for your answer. I usually avoid camelCase/PascalCase filenames, so I hadn't considered that case.
Would you prefer keeping dashCase() for general component discovery and handling h1-h6 specially? I'll propose a change in that sense tonight. Do you have a different approach in mind to fix this overriding of markdown?

[thetutlage]

Yeah, our string utilities are bad with converting properties that contains numbers or dots. So we can be selective about html elements with numbers like headings

[Xstoudi]

I handle titles as specific cases, I didn't find any other html tag that uses number and I could have missed something, but I guess it won't be relevant anyway regarding markdown override. Let me know if something more is required, thanks for the review!

[thetutlage]

👍🏽