Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Markdown provider: malformed content crashes Web #267

Closed
abovedave opened this issue Oct 18, 2017 · 1 comment · Fixed by #342
Closed

Markdown provider: malformed content crashes Web #267

abovedave opened this issue Oct 18, 2017 · 1 comment · Fixed by #342
Assignees
@adamkdean
Labels
type: bug

Comments

@abovedave
Copy link
Contributor

abovedave commented Oct 18, 2017 •
edited
Loading 

---
title: My blog post
author: David
Longworth
preface: Lorem Ipsum Dolor Sit Amet
---

Lorem Ipsum Dolor Sit Amet

Error is:

name: 'YAMLException',
reason: 'can not read a block mapping entry; a multiline key may not be an implicit key',```
@adamkdean
Copy link
Contributor

It doesn't!

🙈

@adamkdean adamkdean self-assigned this Oct 24, 2017
abovedave pushed a commit that referenced this issue Feb 19, 2018
fix: better error catching for malformed yaml
3866db4 
closes #267
@abovedave abovedave mentioned this issue Feb 19, 2018
Merged
abovedave pushed a commit that referenced this issue Feb 19, 2018
fix: better error catching for malformed yaml (#342)
17f813d 
* fix: better error catching for malformed yaml

closes #267

* fix: correct test for empty

* feat: update web-es6-templates

* fix: only send.json if headers not sent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adamkdean adamkdean

Labels
type: bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: better error catching for malformed yaml dadi/web
2 participants
@abovedave @adamkdean