We need a new name.

4 Characters maximum.

Can I have some input on this? Maybe even some name suggestions?

Any idea or feedback is welcome :)

Current Name-Suggestions by probability that I'll take them:

• Chi (.chi, .jade, .jd)
• Shi (.shi, .jade, .jd)
• Inu (.inu, .jade, .jd)

Update (15.12.2016):

Tale Jade will be Phug in the future, a collaboration project of currently existing Jade/Pug implementations

This is kind of annoying bug to my experience. Let's take an example:

-
    /**
     * CakePHP(tm) : Rapid Development Framework (http://cakephp.org)
     * Copyright (c) Cake Software Foundation, Inc. (http://cakefoundation.org)
     */

doctype html

This snippet gives me Jade parse error, it says like this: Failed to parse jade: Mixed indentation style encountered. Dont mix tabs and spaces. Stick to one of both. (Line: 3, Offset: 2)

It would be incredible useful to have support for buffered code blocks, because PHP code is so messy. :)

I have to resort to this hack when dealing with a buffered object:

  -
    $columns = ['id','tracker_id', 'project_id', 'subject',
    'description:ntext', 'issue_category_id', 'user_id', ['class' => 'yii\\grid\\ActionColumn',
     'contentOptions' => ['nowrap'=>'nowrap'] ] ]

  !=GridView::widget(['dataProvider'=> $dataProvider,'filterModel'=> $searchModel,'columns'=> $columns])

I really need help creating more documentation resources.

If anyone is willing to help, I'd provide everything needed including an information channel that knows all deep secrets of Jade (me).

What I need exactly is:

1. PHP Doc Blocks in the 1.5 and 1.6 branches (many doc blocks...)
2. A real (possibly Jade&Bootstrap powered) Open Source website that will be hosted at http://jade.talesoft.io containing
   • The sandbox (Might also be re-written)
   • Installation and usage guides
   • A list of all common features of Tale Jade
   • A list of advanced techniques with Tale Jade (There are quite a few, I just forget them when I try to write them down)
   • A developer's guide for extending Tale Jade (Necessary after 1.5)
3. Maybe a new README that is cleaner to read and references the website correctly
4. Maybe, just maybe, a really cool and actually working phpdoc-template.
5. A logo! (Maybe with a neat Jade-stone or something like that)

Any help is appreciated

Here's an example:

.col.s6.right-align #[strong Sign In] / !{$view->Html->link('Sign Up', ['action' => 'add'])}

This should be interpreted as:

<div class="col s6 right-align">

  <strong>
    Sign In 
  </strong> / <?=$view->Html->link('Sign Up', ['action' => 'add'])?>
</div>

But it's misinterpreted like this:

<div class="col s6 right-align">

  <strong>
    Sign In] / <?=$view->Html->link('Sign Up', ['action' => 'add'
  </strong>)?>
</div>

I confirmed it on talejade sandbox.

I think this is caused by wrong lookup of matching brackets during interpolation processing.

First of all: thanks for making this library!

I am fully aware that it is wet paint, but I've decided to take the plunge - after examining the alternatives - and integrate this with Yii2.

It really threw me for a loop, when I discovered - after many cryptic error messages - that I should not prepend conditional php code with the dash:

if $something
  ..

If would be better, and more consistent, to let that be unbuffered code:

- if $something
  ..

or

-if $something
  ..

If it threw me, it would probably trip someone else up as well. :)

Calling in mixin other mixin defined later in same file with params cause Compiler exception

2 0.0289 334680 Tale\Jade\Renderer->render( ) 3 0.0342 344896 Tale\Jade\Renderer\Adapter\File->render( ) .../Renderer.php:340 4 0.0361 345432 Tale\Jade\Renderer->compileFile( ) .../File.php:173 5 0.0361 345480 Tale\Jade\Compiler->compileFile( ) .../Renderer.php:316 6 0.0389 347288 Tale\Jade\Compiler->compile( ) .../Compiler.php:542 7 0.6745 1275980 Tale\Jade\Compiler->handleMixins( ) .../Compiler.php:476 8 0.7064 1334288 Tale\Jade\Compiler->handleMixin( ) .../Compiler.php:1268 9 0.7065 1334432 Tale\Jade\Compiler->compileChildren( ) .../Compiler.php:1297 10 0.7065 1334916 Tale\Jade\Compiler->compileNode( ) .../Compiler.php:1892 11 0.7065 1335264 call_user_func:{/adv/vhosts/vsk.a.adv.ru/personal/vendor/talesoft/tale-jade/Compiler.php:925} ( ) .../Compiler.php:925 12 0.7065 1335280 Tale\Jade\Compiler->compileMixinCall( ) .../Compiler.php:925

Following example cause this error: `mixin a(a) a= a +b(a) mixin b(b) b=b

+a('a')`

Considering this:

span foo
| bar

The offical Jade engine compiles this to:

<span>foo</span>bar

While Tale Jade gives me this (regardless of the pretty output setting):

<span>
  foo
</span>
bar

So Tale Jade makes it rather hard to have the two parts joined without a space. One of the reasons I love Jade is that it always flattens whitespace, and you have to explicitly add spaces if you want them.

Is there a way that I can create a single file and use for both purpose. One I am loading the contents setting some variable and if the content will send from js it will replace those variables?

This issue is related to include statement.

mixin.jade

h2 Hello

1.jade

include mixin.jade

After compilation, it should generate only 1.html with the following contents:

<h2>Hello</h2>

But the result is it generates 1.html as well as mixin.html. And the contents are not good. mixin.html

<h2>Hello</h2>

1.html

h2 Hello

This is certainly a bug right?

I get this error when I try to use block buffered code:

Failed to parse jade: You should indent in by one level only

This kind of code can reproduce the error:

        -
          $menuItems[] = ['label' => 'Logout (' . Yii::$app->user->identity->username . ')',
                         'url' => ['/site/logout'],'linkOptions' =>['data-method' => 'post']]

When ttl option is set, tale-jade does not care whether source template was changed or not. It just sends cached file to render.

It would be desirable to have an option to check source tempate filemtime() previously. And if source template was changed, regenerate the cache for it.

E. g. 'auto_update' => true|false.

Consider this code:

p #{$var}
    $var

Produces:

<p>
  <?=htmlentities(isset($var) ? $var : '', \ENT_QUOTES, 'UTF-8')?>
  <?=htmlentities($var, \ENT_QUOTES, 'UTF-8')?>
</p>

First occurence was checked by isset, and second was not.

1. Is it possible to configure isset checks to behave the same way through all the code?
2. It is possible to disable isset checks completely?

Using this jade syntax:

script.
  // JS code here...

Without pretty when rendering collapses all the line breaks in the script code without intelligent consideration for semicolons. This breaks most inline scripts if you don't use semicolons, which is valid JS and an enforced coding style in many teams (see JavaScript Standard Style).

Pug has no issues and intelligently minifies the JS inside inline scripts.

It seems Tale Jade does not render boolean attributes smart like Pug does.

button(disabled=true)
button(disabled=false)

Renders:

<button disabled="true"></button>
<button disabled="false"></button>

While:

button(disabled=#{true})
button(disabled=#{false})

Crashes.

button(disabled=(true))
button(disabled=(false))

And:

- $disabled = true;
button(disabled=$disabled)
- $disabled = false;
button(disabled=$disabled)

Both render:

<button disabled="1"></button>
<button></button>

Ideally, specifying true or false would render:

<button disabled></button>
<button></button>

In my component mixins I am resorting to the rather verbose:

- $disabled = false;
button(disabled=($disabled ? 'disabled' : false))

To render:

<button disabled="disabled"></button>
<button></button>

According to the HTML5 spec, boolean attributes should only ever be valueless or contain the exact attribute to indicate true, or contain an empty string or be omitted to indicate false.

In Pug, this:

mixin test
  block

- $text = 'Test text';

p=$text
+test
  p=$text

Renders:

<p>Test text</p>
<p>Test text</p>

In Tale Jade, the very same renders:

<p>
  Test text</p>


<p>
  </p>

This is a big blocker to porting my Pug templates over, not really sure how to handle it.

Found it here

Though, I don't like the system they use, since it reduces the portability of templates (You'd always need the same config file everywhere) and it can confuse people when someone uses @ for role and some @ for data-whatever.

My approach is something similar to Aliases.

shortcut @(role data-role)

nav.main-nav@navigation

resulting in

<nav class="main-nav" role="navigation" data-role="navigation"></nav>

These shortcuts could be defined at the top of your base-layout or in another file that get's included (similar to mixins)