egladman/crunchwrap

Barebones mustache-like templating written in pure Bash. That means no sed or awk.

crunchwrap's Issues

Support filters

Instead of trying to predict everyone's use-cases I'll instead open up crunchwrap and allow variables to be piped to common utilities.

This introduces it's own set of problems though. This would allow the running of arbitrary code. We can take some steps to lockdown filters, but it's not a catchall. There will always be ways to circumvent any sense of security given the user is entering input.

Someone could easily wreck havoc with a oneliner like:

{{ variable | true && rm  -rf $HOME }}

Here's some steps we can do to safen filters, but again it's not a catchall.

• whitelist specific commands such as:

  • gawk
  • awk
  • sed
  • cut
  • grep
  • egrep
  • tail
  • wc
  • sort

• kill filter/command if it runs for more than X seconds

As I start to build out this feature I'm sure I'll find more ways to improve the concept.

Implementation Example

Variable:

example_var="The quick brown fox"

Template:

{{ example_var | awk '{$2="slow"; print $0}  }} jumps over the lazy dog

Output:

The slow brown fox jumps over the lazy dog

Refactor

Problem

functions like _eval_tags and _parse are begging to be rewritten. Their far too big, and difficult to follow.

What needs to be done

• Before proceeding I need to write tests to insure I don't inadvertently break anything
• Reduce function line counts
• update styling/function naming convention similarly to what's found in egladman/squib