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

Invent a better framework to develop templates #49

Open
Ledoux opened this issue Feb 10, 2017 · 0 comments
Open

Invent a better framework to develop templates #49

Ledoux opened this issue Feb 10, 2017 · 0 comments

Comments

@Ledoux
Copy link
Owner

Ledoux commented Feb 10, 2017

This is for now a big weakness of the framework:

As template (specially frontend templates) are juste static files that need some other templates in order to be tested in a full application state. Annoying workflow for now is either:

  • create a full app, and then extract from the app the files that are consistent for doing themself a template package.
  • or create a project with the dev template already defined, go to the node_modules, rm -rf <test_template>, symlink the one you have locally, do some changes in this node_modules symlinked folder, and trigger manually a tpt dump/tpt configure/tpt replace, anytime you made a change to see the effect on the app.

So we cannot directly go the repo of the dev template, change code and see an automatic livereload of the changed in a testing app.

At some point it would be cool, to have a tpt test CLI that is able to embed the template into a testing app, that also watches the file changes and so trigger the dump, configure, and replace sub tasks in the tested app.

@Ledoux Ledoux changed the title Invent a better framework to dev templates Invent a better framework to develop templates Feb 10, 2017
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

1 participant