List view
Name Change. A new repository will be created, this one will redirect to the new one. The composer name will change as well as the namespace. This change won't be backward compatible in any way.
Overdue by 10 year(s)•Due by May 27, 2016•1/1 issues closed1.4.3 is a small minor bugfix patch for the current Tale Jade structure.
Overdue by 10 year(s)•Due by May 24, 2016•2/2 issues closedThis will be a feature update based on 1.5 The following features will be added: - Dynamic includes (#72) - Multiline Markup (#71) - `&attributes` will do the exactly the same as in official Node.js (right now it's thows an exception :)) (#11) - There will be aliases. Like mixins, just shorter. (#10) A small example: ```jade alias btn a.btn.btn-block btn.btn-primary(href='#')= My awesome button! ``` The alias jade and the jade that calls the alias gets merged. I'm really undecided if there will be a prefix or not. I'd rather have it as "replace that specific element", but we'll see - Import arguments. You can pass new variables to imported files, which will also work with dynamic includes. (#6) Example: ```jade header include awesome-nav(orientation='vertical', theme='inverse') footer include awesome-nav(orientation='horizontal') ``` - PSR-6 compatible caching mechanism (probably based on tale-cache) - More stuff I will add here later What I plan, but what is not subject to be implemented yet: - Tokenize PHP expressions and filter out specific tokens (e.g. disallow the use of functions, disallow specific functions, disallow a bunch of other stuff) Thanks for your interest!
Overdue by 10 year(s)•Due by June 29, 2016•0/7 issues closedTale Jade 1.5 will be the first completely breaking change. **You might always stick to 1.4.*, since 1.5. won't introduce new features, I promise!** It will be a structure overhaul. Things that got changed already: - Lexer has been split into Tokens, Scanners, a State and the Lexer that composes them - The lexer now uses tale-reader, which is a string-parsing library fit to Tale Jade's needs (and possibly other lexers I will write in the future) - tale-tree now replaces every tree-logic inside tale-jade - Parser has been split into a ton of Nodes, a State and the Parser that composes them - Instanciation now uses tale-factory to avoid a ton of necessary checks - Lexer can be extended easily, either by adding Scanners that throw out existing tokens or by adding completely new tokens. Both are just extending a class and adding a config value to the lexer (or extending the lexer, whatever you prefer) - Complete PSR-2 overhaul. No underscore-prefixes. - All config keys of all classes will be under_scorized, not camelCased anymore (primarily to fit Symfony's style) Things that will be changed: - The Compiler will get a full overhaul and will use a Formatter and probably some further classes for a modular structure to easily extend it (I'm not done yet, I didn't find the best structure yet and that is probably the main reason why 1.5 is not released yet) - Filters will be changed and will give a possibility to change deeper parts and format filterered content easier - All functions have been put into a small Utility that will be compressed and compiled in stand_alone mode Things that might be important: - Tale Jade now handles scalars quite differently. Before a code like `a(class=col-md-5)` renderered to `a(class="col-md-5")`. It will now probably throw an error, because it tries to subtract the constants `col`, `md` and the digit `5`. A scalar string will now be a scalar string only if it's enclosed in quotes of any kind. Everything behind = is essentially PHP (or rather, an expression. That won't mean that all attribute values get printed as PHP. Tale Jade now checks for scalar values quite cleaner Also, some more stuff I can't think of at the moment and will add here later probably. Thanks for your interest!
Overdue by 10 year(s)•Due by May 30, 2016•3/5 issues closed