Skip to content

eliminate crash on warnings generated by README.md #1410

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

Merged
merged 5 commits into from
May 10, 2017
Merged

Conversation

jcollins-g
Copy link
Contributor

fix #1409.

This fixes the bug by eliminating the second pathway to _renderMarkdownToHtml, forcing packages down the same path as every other Documentable.

@jcollins-g jcollins-g requested a review from keertip May 10, 2017 17:32
@googlebot googlebot added the cla: yes Google CLA check succeeded. label May 10, 2017
@jcollins-g jcollins-g requested a review from devoncarew May 10, 2017 17:33
@jcollins-g jcollins-g changed the title Readme warnings eliminate crash on warnings generated by README.md May 10, 2017
}
if (refElement is PrefixElement) {
// We found a prefix element, but what we really want is the library element.
refElement = (refElement as PrefixElement).enclosingElement;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is actually a second bug that was lurking behind the first one: commentRefs can contain PrefixElements.

@jcollins-g jcollins-g merged commit b353c7b into master May 10, 2017
@jcollins-g jcollins-g deleted the readme-warnings branch May 15, 2017 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Google CLA check succeeded.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression: new warning system unable to handle warnings caused by package README.md
3 participants