Different Objective-C categories on an external type get merged together

[1ec5]

In an Objective-C project, I have two distinct categories on NSValue, but they get merged into one. The merged category takes the name of one of the original categories and now one of my custom_categories is incomplete. This seems to match the behavior requested in #457. Merging categories into the parent documentation makes sense as long as the parent documentation is part of the same docset. But categories on an external class, such as this Foundation class, should be kept separate.

[jpsim]

Thanks for reporting this, and yeah I'd consider this a bug because it differs from the Swift behavior. If you add extensions to types declared outside your module, they don't get coalesced, they remain distinct.

[jpmhouston]

This is affecting my project too. I'm be willing to do some debugging, can anyone give me tips on where in the source to start looking, and tips for debugging (I using homebrew-installed ruby, last couple times I tried getting some debugger tools I either found a deadend or got lost).

[karagraysen]

Saw a few PRs merged that mentioned this issue. What's the progress on this?

[1ec5]

No progress. That's just me referring to this issue when working around it in a library I'm working on.

[karagraysen]

Thanks for clarifying!