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

Moban extension #61

Merged
merged 23 commits into from
Jun 8, 2018
Merged

Moban extension #61

merged 23 commits into from
Jun 8, 2018

Conversation

chfw
Copy link
Member

@chfw chfw commented Jun 8, 2018

Delivers solution for the following issues:

#23
#18
#26

@chfw chfw requested a review from jayvdb June 8, 2018 07:35
@codecov-io
Copy link

codecov-io commented Jun 8, 2018

Codecov Report

Merging #61 into dev will increase coverage by 0.11%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##              dev      #61      +/-   ##
==========================================
+ Coverage   98.77%   98.89%   +0.11%     
==========================================
  Files          27       32       +5     
  Lines        1146     1266     +120     
==========================================
+ Hits         1132     1252     +120     
  Misses         14       14
Impacted Files Coverage Δ
moban/copier.py 96.42% <ø> (ø) ⬆️
moban/hashstore.py 100% <ø> (ø) ⬆️
moban/tests/files.py 100% <100%> (ø)
tests/test_copier.py 100% <100%> (ø) ⬆️
moban/filters/github.py 96.96% <100%> (+0.09%) ⬆️
tests/test_docs.py 100% <100%> (ø) ⬆️
tests/test_filter_repr.py 100% <100%> (ø)
moban/mobanfile.py 96.42% <100%> (+1.55%) ⬆️
moban/engine.py 98.61% <100%> (+0.19%) ⬆️
moban/filters/text.py 100% <100%> (ø) ⬆️
... and 11 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 55d64f8...4462f8f. Read the comment docs.

@chfw chfw merged commit 0a20599 into dev Jun 8, 2018
@chfw chfw deleted the moban-extension branch June 8, 2018 22:07
targets:
- filter.output: filter.jj2
- test.output: test.jj2
- global.output: global.jj2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eol at eof

Everything is up to date!

Please examine individual template and its associated plugin for more details.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary trailing blank line?

Hello, you are in level 7 example
{% else %}
Hello, you are not in level 7
{% endif %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eol at eof

{%else%}
no
{% endif %}
{{ test }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eol at eof

chfw added a commit that referenced this pull request Jun 9, 2018
chfw added a commit that referenced this pull request Jun 11, 2018
* ✨ choose a template based on its file extension. fix #43

* 📚 update change log

* 🐛 fix the template names

* 📚 udpate readme

* ✨ default template engine will be jinja2 if template type(file extension) cannot be found

* 👕 address review feedback. #61

* 🎨 keep cli --template_type option

* ✨ allow template_type in moban file to indicate default template engine. i.e. if unknown template type(file suffix) is found, the default template engine is used. So if mako engine is specified via template_type, an unknown template file such as strange.template will be rendered by mako engine

* ✨ allow jinja2 become template suffix too, meaning a.jj2 and b.jinja2 will be rendered by the same engine. however, for now, the engine instance will not be the same. later on, this can be consolidated

* 📚 update change log. #58

* ✨ associate jinja2 engine with more file types, j2, jinja and retore the default template engine name as jinja2

* 📚 documentation update
chfw added a commit to moremoban/moban-handlebars that referenced this pull request Nov 18, 2018
* ✨ choose a template based on its file extension. fix #43

* 📚 update change log

* 🐛 fix the template names

* 📚 udpate readme

* ✨ default template engine will be jinja2 if template type(file extension) cannot be found

* 👕 address review feedback. moremoban/moban#61

* 🎨 keep cli --template_type option

* ✨ allow template_type in moban file to indicate default template engine. i.e. if unknown template type(file suffix) is found, the default template engine is used. So if mako engine is specified via template_type, an unknown template file such as strange.template will be rendered by mako engine

* ✨ allow jinja2 become template suffix too, meaning a.jj2 and b.jinja2 will be rendered by the same engine. however, for now, the engine instance will not be the same. later on, this can be consolidated

* 📚 update change log. #58

* ✨ associate jinja2 engine with more file types, j2, jinja and retore the default template engine name as jinja2

* 📚 documentation update
chfw added a commit to moremoban/moban-handlebars that referenced this pull request Nov 18, 2018
* ✨ choose a template based on its file extension. fix #43

* 📚 update change log

* 🐛 fix the template names

* 📚 udpate readme

* ✨ default template engine will be jinja2 if template type(file extension) cannot be found

* 👕 address review feedback. moremoban/moban#61

* 🎨 keep cli --template_type option

* ✨ allow template_type in moban file to indicate default template engine. i.e. if unknown template type(file suffix) is found, the default template engine is used. So if mako engine is specified via template_type, an unknown template file such as strange.template will be rendered by mako engine

* ✨ allow jinja2 become template suffix too, meaning a.jj2 and b.jinja2 will be rendered by the same engine. however, for now, the engine instance will not be the same. later on, this can be consolidated

* 📚 update change log. #58

* ✨ associate jinja2 engine with more file types, j2, jinja and retore the default template engine name as jinja2

* 📚 documentation update
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

Successfully merging this pull request may close these issues.

3 participants