Ben Hockey

even though this PR was presented as a way to parse return descriptions, one of the key pieces of this PR is breaking out `processMetadata` so that it can be...

i just came across this same issue... when `generateMetaData` handles `'Property'` types, if the property happens to be for a value that already has metatdata then we mixin/override the summary...

> i wonder if it would hurt anything if we changed it to propertyValue = read(property.value, { asIdentifier: true });. it does hurt... very badly - so that might not...

by default, a property's metadata is a copy of the value's metadata but in `generateMetadata` we have enough context to know when a property's metadata should override the value's metadata....

to doc any property that maps to a node (in a template or not), the simplest solution might be: ``` js declare( ... , { /*===== // focusNode: DomNode //...

i think e8d05e3 from #80 may resolve this but i'm not sure. it would be worth verifying.

i believe that d86cc3a in #80 would fix this.

e8d05e3 in #80 would fix this. #82 has an explanation.

i can't reproduce this with the [current master](00cc4baed957f906ae98fc99e86b44e75452c69f) in this repo. is it still a problem?

i think this original issue would be fixed by d86cc3a in #80