Custom tags/extensions about markdown HOT 3 CLOSED

What exactly about the above is not possible with the current extension mechanism described in the README?

from markdown.

Sorry, I wasn't clear. The extension code works fine - I've added custom tags.

However, the extension tag syntax is not standardized. Right now, I could add the dog tag, with this syntax:

dog 666

Jerry adds the cat tag:

[[cat id:666]]

You add the wombat tag:

++wombat id="666"+++

Authors would have a hard time using all three, without going crazy. Extensions don't combine easily, so there is less accumulation of functionality over time, and less building on each others' work.

A standard extension syntax and a accompanying class would make it easier to create extensions that obeyed the syntax rules. For example:

class DogTag extends CustomTag {
  protected $tag = 'dog';
  protected $arg_defs = array('name', 'breed');
...
  function something() {
    if ( $this->args->breed == 'black lab' ) {
      echo 'The best ever!';
    } 
...
}

The tag syntax might be:

{{dog breed="black lab" name="Oscar" /}}

The human writing the dog extension wouldn't have to manually parse the arguments, mess with { or /.

Good work on the library, by the way. Berlin must have something in the water to make such good developers.

Kieran

from markdown.

I read the issue twice but I do not understand what to do with it. This library implements markdown parsing using extisting standards, I am not going to develop new markdown syntax. That is possible in your own application or library by extending the classes provided by this library.

from markdown.