-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed and Improved Multi-Markdown metadata support #49
Fixed and Improved Multi-Markdown metadata support #49
Conversation
@oliviermartin |
Hello,
On 30 December 2014 at 11:15, Paul Verest notifications@github.com wrote:
Dr Daniel Winterstein A: CodeBase Argyle House, Edinburgh, EH3 9DR |
@winterstein Dan, merge when you like and have no questions. then discuss in #52 if to release 1.2 |
@oliviermartin this one can't be automatically merged. Could you please update it to be on top of already merged #48 #50 #51 |
Then I am to be build and test locally If OK, I am going to release this January #52 |
We only want to catch metadata keywords. Other lines were caught with the former regular expression such as heading containing a colon.
…e valid Prior to this change, metadata were parsed even if the metadata block was not valid. Example of non valid metadata block: --------- Author: Olivier --------- The MultiMarkdown format requires an empty line to be added at the end of the metadata block.
b570849
to
7183192
Compare
Sorry, I missed your comment about the patch conflict. This new version should fix it. |
great |
Fixed and Improved Multi-Markdown metadata support
please check/improve README 5c3a320 |
This patchset allows: