-
Notifications
You must be signed in to change notification settings - Fork 20
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
File templates - additional features #42
Comments
Hi @chuckhendo, Thanks for your great suggestions. I added templates at one point but haven't had the time to write documentation or really configure them for my own use case. I think the first two suggestions are stuff we can totally add out of the box. We could do the variable replacement part in a naive way first where we basically provide:
If people like it and want more configuration we could explore if there would be a nice way to interop with the extension you linked using I get your idea with the third bullet point but I'm wondering how we would build this in an easy to configure way without having to add too much redundant code. It seems to work well with your example above but the question would be how it would interact with the other configuration options. As for the fourth one, I think that's something that we could add without adding too much configuration complexity. Especially if we do it in the way that the selector box only shows up if there are multiple templates for the same extension. Right now this should be possible if you would name your files like I think we should start with the first two features and improve the documentation on the templating feature. Once we have that going we could dive into the other ones. What do you think? Cheers, |
Great idea! I'll be able to take a look at that in a few weeks |
@chuckhendo Any feedback on this? |
@Telokis I keep wanting to take a look at it, but I just haven't had the time recently. Hope I can real soon |
I see that file templates were recently added, although there really isn't much documentation on them. I wanted to see if you had any additional plans on what direction you want to take file templates, particularly in regards to the list below. I would be happy to do any/all of the work for this, but I don't want it to interfere with your plans. Some of it might also belong in a completely separate extension.
".js": "./templates/Component.js"
to tell it to look for the files in the project folder. This makes sense as my JS templates may change from project to project, and these would also be able to be shared with other users of the projectVery curious to hear your thoughts here, @dkundel. I've thought about building a extension to do this style of templating for a while, but I really like this extension, and would rather contribute if it makes sense.
The text was updated successfully, but these errors were encountered: