:markdown filter processing the text of a String variable

[bobmonteverde]

So I have a variable that's a sting containing markdown text (the body of an article for a simple node powered blog).

so, first I tried:

:markdown
  #{ article.body }

which outputs: <h1>{ article.body }</h1>

I also tried:

:markdown
  \#{ article.body}

which outputs the contents of article.body, BUT does not process the contents with the markdown filter.

So, is there a way to accomplish what I am trying?

[bobmonteverde]

I ended up just using markdown.toHTML function, to process the markdown to html before sending to the template. I guess that works, though I think it would be nice to be able to do this just in the template

[tj]

ah, the filters are actually compile-time to avoid wasting resources per request. you could expose a helper and just do p!= markdown(article.body)

[shinuza]

Can't the filters receive the parent context? I'm trying to figure out a way to do this as well.

[tj]

filters are compile-time, most of them are things like coffeescript, markdown, stylus etc so compiling them per-request would be really wasteful

[shinuza]

OK, is there another way to extend Jade with features like what you can do in Django?

Edit: I'm trying to compile a set of basic features you would want to use in templates. I trying to find the simplest way for them to be available for template authors.

I'm guessing filters in Jade are not the same as filters in Django.

[tj]

you can just use functions, pass them as locals, or in express there are many ways to expose helper functions

[tj]

This issue has been inactive for over 1 month so I'm closing it. If you think it's still an issue re-open. - tjbot

[jwerre]

I used express-expose

[Denis535]

Much time has gone. Is still there no way to pass text variable to filter?
What's problem to do something the next?

:markdown-it(content=article.body)

Or

:markdown-it= article.body

I think in most cases it is necessary to pass text in variable.

[TimothyGu]

https://github.com/pugjs/jade/blob/master/docs/views/reference/filters.jade:

Filters are rendered at compile time, which makes them fast but also means that they cannot support dynamic content or options.

They are designed to not support dynamic content.

[Denis535]

This is strange. I don't see any difference. Filter the text from current jade file or take the text from the locals.

[ForbesLindesay]

There are two stages to generating html from jade. The first step (compiling) happens once on application startup, and doesn't have access to local variables, only to the raw source code. The second stage (rendering) happens for every single page request. It's responsible for combining the compiled code with the locals. It's critical that this stage is really fast.

[ghost]

I use pugjs to generate html files much like in statically generated websites. For this, it would be very useful to generate html from markdown using variables.

[buckle2000]

:markdown-it= article.body

I feel like this should work somehow.

It doesn't even throw an error.