-
Notifications
You must be signed in to change notification settings - Fork 184
Support for custom template paths, additional improvements #727
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
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. |
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. |
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. |
I'm happy to write up additional use cases or tests as wanted! |
@k1LoW Let me know what you think 😄 |
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. |
@k1LoW I split those up into issues and linked them here 👍 |
This PR adds:
Enum
template in markdown (Closes Support for generating Enum description files #729 )shortName
template field/attribute (Closes Support shortName table property for Markdown templates #730 )Description
section in generated Markdown output #731 )This code was written with the help of Claude 4.0