Uh oh!
There was an error while loading. Please reload this page.
This repository was archived by the owner on Jul 6, 2026. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can't be
null;.First()requires that an element be returned, and unless we have a bug and we do.Returns.Add(null), there should only be non-nullelements withinjdi.Returns.If we want to allow
null, use.FirstOrDefault().Actually, on review this entire block doesn't quite make sense to me:
ritself shouldn't change fromr.Add(), and thus this should be a no-op (unlessjdi.Returnssomehow has > 1 element in it? But how could that happen?)Neither of the above statements should be needed.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The null check was intended to handle the possibility of
jdi.Returns.First ()not being anXElement, though I think we only ever addXElements to thisICollection<XNode>in the section above and so the check probably shouldn't be needed.The
FinishParse (context, parseNode).Returnscollection will have more than zero elements in it when the<javadoc>entry that is being parsed has multiple@returnvalues in it, as shown in the test addition below. TheReturns.ClearandReturns.Addadditions do look to be redundant here though, I will clean that up.