npm publish --access public // "publish": "npm publish --access public"
- <input disabled="" type="checkbox"> slots for in-source code gen => example 2: C# class to list constraints
- <input disabled="" type="checkbox"> use basic snippets to mirror example 1's README to main README file with variable for links (RELATIVE_FILE_PATH)
- <input disabled="" type="checkbox"> -- %&: @=: ADD_tests="" OBJADD_tests="[]" CAPTURE_constraints = "([.+][.+])" => _constraints=[ ["[dbo].[...]"] ]
- <input disabled="" type="checkbox"> LINE_SELECT="\s//(.)"
- <input disabled="" type="checkbox"> USING="plugins/xmldoc" ARGS="--target md"
/* .... :constraint_constants <%= constraints.join(",\r\n") %> */ // &<:constraintconstants // &>
You can even use EJS template to generate CFL which can produces EJS, and that opens a higher level of meta, which probably will be :)
Make migration scripts for arbitrary script files according to marker lines
Name ideas:
- code-formation
- cftk
- cft.js
;;; (defvar x 5) ;;; (begin a) ;;; (end a) ;;; (snippet begin a) ;;; (snippet end a)
;;; (template begin )
- <input disabled="" type="checkbox"> configurable prefix $$$ %%%
- <input checked="" disabled="" type="checkbox"> include chalk, pretty print
- <input disabled="" type="checkbox"> scan variables: |: _x=5 ||: _x=5
scan snippets: $< or $@<
$> or $@>
- <input disabled="" type="checkbox"> inject snippet: $!:abc
scan plugs: %< or %@<
%> or %@>
scan slots: &< or &@<
&> or &@>
export evaluation includes EJS template render
- <input disabled="" type="checkbox"> capture evaluation
- <input disabled="" type="checkbox"> snippet evaluation at the end
- <input checked="" disabled="" type="checkbox"> command line arguments
- <input disabled="" type="checkbox"> variable syntax: {CURRENT_FILE} "${CURRENT_FILE}"
- <input disabled="" type="checkbox"> inline syntax that allows regex search/replace: --
-- $<:delete_object_if_exists type="default_type" a=_abc b="[abc]" prefix=" "
delete <%= type %> <%= name %>
-- $>