Migrate To Parsedown Extra For V2.0 about laravel-markdown HOT 18 CLOSED

+1. Good call.

Actually I use it for a few weeks. Definitely better and faster than others. In previous releases parsedown was not good enough but for today, this is not a problem. Also keeping development each day.

from laravel-markdown.

@metude This is now available on the develop branch. Note that the develop branch is targeting Laravel 4.2 now. I plan to release Laravel Markdown 2.0 in July this year, but the develop branch is aliased to 2.0, so if anyone wants to try it before then they can. Truth be told, I won't be doing much work on it from now until release, so it's not going to change much from how it is now.

EDIT: Laravel Markdown 2.x will support Laravel 4.1, 4.2, and 4.3.

from laravel-markdown.

So your recommendation is using develop branch with 4.2? Or should I hold on the 4.2 upgrade until 2.0 is released in July?

from laravel-markdown.

@iBotPeaches There's not much point in waiting for this package to make a stable 2.0 release if you want the new stuff in laravel 4.2. I'm pretty much done with the updates for 2.0 now after I pushed 881e7e5. That commit means than we can now use laravel's view functionality to render pages in .md, .md.php and .md.blade.php, in addition to still using the render function that's available on the Markdown class. I'm unlikely to make any more breaking changes. If I do, I'll notify everybody on this issue. You can see the differences between the current stable release and the development version here: master...develop.

The best course of action for how would be to:

{
    "require": {
        "laravel/framework": "4.2.*",
        "graham-campbell/markdown": "~2.0@dev"
    }
}

Also, it's important to note that this package will be keeping support for laravel 4.1.

Just to say this again:

Laravel Markdown 2.x will support Laravel 4.1, 4.2, and 4.3.

from laravel-markdown.

Just a quick note about a bc break I just made. After my last commit, if you are injecting this class through typhinting etc, you'll need to type hint GrahamCampbell\Markdown\Markdown now instead of GrahamCampbell\Markdown\Classes\Markdown. I'm doing similar things over my other packages as they head towards a major version bump.

from laravel-markdown.

Is there to be an update to use Parsedown Exra? Is it possible to use now via a config option for the package? https://github.com/erusev/parsedown-extra

from laravel-markdown.

@ryanscherler I'll be doing this as soon as a release is tagged on that repo.

from laravel-markdown.

Oh, I see one has been tagged. I'll upgrade to it later today.

from laravel-markdown.

Done.

from laravel-markdown.

Thanks Graham! Updating now.

from laravel-markdown.

I just updated to the latest. Is there a config option to enable "extra" parsing options? e.g. I want to use the extra class options for an image for example {.class}

from laravel-markdown.

I'm not sure what you mean. Parsedown extra should be allways enabled now.

from laravel-markdown.

I updated my composer version to the latest as noted in the readme and then ran an update. After that I tried to run my app and see if the new parser was kicking in the additional class attributes and it was still just showing the brackets after the image. Not sure why its still behaving as it was before?

from laravel-markdown.

Here is a screenshot of my app with the sample text I am using to try and render:

from laravel-markdown.

@ryanscherler This is behond the scope of this packge. Please take this up with parsedown extra itself: https://github.com/erusev/parsedown-extra/issues/new.

from laravel-markdown.

Ok will do ;-) Thanks for providing this wrapper and I am sure it will resolve over time with parsedown extra.

from laravel-markdown.

Cool. Be sure to check out the new integration with the laravel view system v2.0 of this package will ship with.

from laravel-markdown.

I've just tagged a release candidate. I'll do a full release in a week or so if no other problems arise.

from laravel-markdown.