Skip to content

Support for custom template paths, additional improvements - #727

Open
reteps wants to merge 10 commits into
k1LoW:mainfrom
reteps:stengerp/template-paths
Open

Support for custom template paths, additional improvements#727
reteps wants to merge 10 commits into
k1LoW:mainfrom
reteps:stengerp/template-paths

Conversation

@reteps

@reteps reteps commented Jul 21, 2025

Copy link
Copy Markdown

This PR adds:

This code was written with the help of Claude 4.0

@reteps reteps changed the title [WIP] Support for custom template paths Support for custom template paths Jul 21, 2025
@reteps reteps changed the title Support for custom template paths Support for custom template paths, additional improvements Jul 21, 2025
@k1LoW

k1LoW commented Jul 21, 2025

Copy link
Copy Markdown
Owner

Thanks for the contribution!

I don't understand why this fix is needed, and there are many fixes in one. I cannot accept it at this time.

@reteps

reteps commented Jul 21, 2025

Copy link
Copy Markdown
Author

Hi @k1LoW -- if I split each change up into it's own PR, would that help each feature be accepted? These features are super useful for customizing the output of tbls for our project.

@reteps

reteps commented Jul 21, 2025

Copy link
Copy Markdown
Author

To provide some more context, I am trying to replace our in-house solution with tbls, and these are the minimum features to add to replace it. The path templating is useful because it gives us extra flexibility in creating directories/files in our preferred structure.

@reteps

reteps commented Jul 21, 2025

Copy link
Copy Markdown
Author

I'm happy to write up additional use cases or tests as wanted!

@reteps

reteps commented Jul 24, 2025

Copy link
Copy Markdown
Author

@k1LoW Let me know what you think 😄

@k1LoW

k1LoW commented Jul 24, 2025

Copy link
Copy Markdown
Owner

It would be great to know in what cases each modification would be useful and why it is necessary (and why it needs to be incorporated as a feature in tbls).

It may be less costly to have the conversation in an Issue rather than splitting this Pull Request first.

@reteps

reteps commented Jul 24, 2025

Copy link
Copy Markdown
Author

@k1LoW I split those up into issues and linked them here 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants