feat: Add partialsDir.rename option

[djaax]

We need more flexibility when it comes to naming partials and don't want to be constrained by our folder structure.

For example, we have

/components
    /button
        button.hbs
    /template
        otherTemplate.hbs

Currently, this names the partial button/button and template/otherTemplate.

This renaming function allows more flexibility, e.g., naming the two templates button and otherTemplate, ignoring the folder structure.

[UziTech]

Currently, this names the partial button/button and template/otherTemplate.

Why are those not good names? Is there a reason you need "better" names?

[djaax]

Continuing the example above, we want to have the template next to other files, e.g. a JS or CSS file organized in subfolders in components. So, next to button.hbs there could be button.js, button.css.

Without the renaming function, the partial's name would be 'button/button' which is redundant and doesn't work with our implementation. Without the renaming feature, we'd have to keep all templates in one partials dir.

[UziTech]

'button/button' which is redundant and doesn't work with our implementation

why doesn't it work with your implementation?

Why is is being redundant a bad thing? It shows the path to the partial so it is easy to find.

I'm trying to understand if this is a "need" or a "want". Or if there is a better way to accomplish the "want".

This doesn't seem like a feature that would be very useful to many users so it would be better if there is a way to handle it without causing feature creep

[djaax]

I understand your concern. I try to explain why we want/need it and you can decide if it potentially helps others or if it qualifies as feature creep.

We're using things like {{> (lookup . 'type') this }} which automatically loads the partial. In the configuration type is, e.g., button (not button/button).

Renaming the partial would be the most elegant solution for us. But sure, there are workarounds, mapping the type with the partial path, etc.

Again, if you deem this unnecessary feel free to ignore this PR.

[UziTech]

Do you have a workaround that currently works?

[djaax]

Well, yes, not organize handlebar files/partials in component folders but one single partial folder. Not ideal but it's ok.

[github-actions]

🎉 This PR is included in version 5.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[UziTech]

Thanks for this! Sorry it took me so long to review.

[djaax]

Thank you, I appreciate it!