Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use ~/.polymorph dir
// Do not merge, the idea is to integrate it into a devel branch and keep working on it, but I can just PR to master.
This improves
Polymorph
to be able to store all files (conditions, templates, temps, ...) inside a$home
based polymorph directory.By default this points to
~/.polymorph
, and at init time it ensures that the needed structure existsIn this case, we validate:
New
settings
class supports us to set library based properties and prerequisites.It adapts all IO operations to use new settings.paths
It also provides a new way to perform hot module loading based on the imp library, see new method
utils.import_file
Additionally, templates save process ensures that .json extension is included, and dumps the template to the templates folder
~/.polymorph/templates
.WIP, some things to do
Will fix #2