Skip to content
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

Notes on possible functionality improvements to autogen #128

Open
2 tasks
WasabiFan opened this issue Nov 26, 2015 · 3 comments
Open
2 tasks

Notes on possible functionality improvements to autogen #128

WasabiFan opened this issue Nov 26, 2015 · 3 comments

Comments

@WasabiFan
Copy link
Member

Here's a quick list of features I think it might be worth adding (for a TODO list / general discussion if needed):

  • Ability to mark sections of code to be templated inline for sections that aren't worth a new template file. This would allow you to do something like this (although probably with slightly different syntax):
doAThing();
//~autogen
doOtherImportantThing({{myClass.myProp}});
//~autogen
  • Ability to include templates in other templates (mark a template to be re-evaluated after initially being inserted)
@ddemidov
Copy link
Member

Ability to mark sections of code to be templated inline

What will happen to this after the first generator run? The liquid code will be replaced by normal code, right? So the code has no special meaning to autogen system, and subsequent generator runs won't be able to update the code?

@WasabiFan
Copy link
Member Author

That's my "slightly different syntax" note 😉 I'm still thinking about it -- do you have any ideas there? My hope was that it would be autocompleted and syntax highlighted by an IDE normally, so it couldn't just be in a comment... hmmmm 😕

@ddemidov
Copy link
Member

I have no ideas. I don't see how we can make same code to be accepted both by compiler/interpreter and autogen unless its in a comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants