-
Notifications
You must be signed in to change notification settings - Fork 101
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
RFC: allowing to save template for later use? #80
Comments
From what I've seen of GitHub templates, they don't have enough features to replicate this package. Hopefully in the future though! On saving: would simply using the Serialisation stdlib do what you want? |
I think any serialization functionality can do the job! but I think it would be nice to have this directly in the package. the point is after being able to save the template configuration to a file, I could share it, re-edit it and put it public. And next time if I want to generate a package, I can just type one line without choosing anything else. regarding to github template: I think we can just consider github template as serialization format for a package, it won't contain any further info except a configured template |
The following does not work, but should.
If that worked all one would need to do is
@Roger-luo for interest, what Invenia does internally is have a private package: I wonder if we should actaully create a PkgTemplatesCommons.jl |
I don't think the recommendation to output Julia syntax has ever been more than a recommendation. |
I'd probably just recommend using Serialization, or doing something like this in template() = Template(; #= ... =#) That way it's up to you to |
it is a strong recommendation though, There is a way you can have both by using the Mime String. Discussion here |
@oxinabox Thanks, I agree with you, we could have some sort of common template package that provides and share some common templates that allows you generate a package with only one button. |
#61 includes a short doc section with recommendations for saving (which could certainly be expanded) and |
It feels annoying that each time I create a template and I have to create it again after I exit REPL. It would be nice if we could have
A proposed workflow is to extend the
generate
function to accept a new keyword which would looks likeand for
interactive_template
, it would search a local folder to check if there is a previous saved template first.we could have a
save
function that saves a generated template object to a folder insidePkgTemplates
folder, or an external repo. I'm wondering if people would like this feature.The text was updated successfully, but these errors were encountered: