You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a project which is basically an extension on NSObject. Without the documentation on extended Objective-C objects, the doc generated by DocC is completely useless for my project.
Importance
I think this feature is relatively important. I am trying a very ugly workaround for the time being, but this would simply not work for a bigger project.
Extension-only frameworks are not uncommon and documenting them should, IMHO, be possible, even for Objective-C projects, especially since DocC has official support for Objective-C.
Alternatives Considered
For now I’m trying a workaround with a separate target where a custom object, subclass of NSObject is created and the extension on NSObject are done on this custom object just for the documentation.
It’s ugly and absolutely not scalable, and I’m currently not even sure it’ll work.
The text was updated successfully, but these errors were encountered:
Feature Name
Document Objective-C Extensions
Description
Implement #210, but this time for Objective-C.
Motivation
I have a project which is basically an extension on
NSObject
. Without the documentation on extended Objective-C objects, the doc generated by DocC is completely useless for my project.Importance
I think this feature is relatively important. I am trying a very ugly workaround for the time being, but this would simply not work for a bigger project.
Extension-only frameworks are not uncommon and documenting them should, IMHO, be possible, even for Objective-C projects, especially since DocC has official support for Objective-C.
Alternatives Considered
For now I’m trying a workaround with a separate target where a custom object, subclass of
NSObject
is created and the extension onNSObject
are done on this custom object just for the documentation.It’s ugly and absolutely not scalable, and I’m currently not even sure it’ll work.
The text was updated successfully, but these errors were encountered: