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.

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

Render bad usage of markdown as empty strings #91

Merged
merged 1 commit into from
Sep 30, 2016

Conversation

kevindew
Copy link
Member

Prior to this change [embed:attachments:filename.jpg] would be
rendered on the frontend amongst the content. This change means that it
would be rendered as an empty string.

Although it is debatable which route is better, having this render empty
strings does allow us to resolve some issues with missing attachments on
Specialist Publisher.

Prior to this change `[embed:attachments:filename.jpg]` would be
rendered on the frontend amongst the content. This change means that it
would be rendered as an empty string.

Although it is debatable which route is better, having this render empty
strings does allow us to resolve some issues with missing attachments on
Specialist Publisher.
@kevindew kevindew force-pushed the gracefully-failing-elements branch from 7daaffe to 1edcb6b Compare September 30, 2016 15:36
@danielroseman danielroseman merged commit f633d2f into master Sep 30, 2016
@danielroseman danielroseman deleted the gracefully-failing-elements branch September 30, 2016 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants