-
Notifications
You must be signed in to change notification settings - Fork 414
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
Extensions documentation is ignored #454
Comments
I'm having the same problem in an Obj-C project. This category ends up being "Undocumented": /// See PSPDFPresentationActions.h for compatible keys for `options`.
@interface PSPDFViewController (Presentation) Whereas this category ends up being documented: /// This defines shortcuts that will edit the `fontAttributes` dictionary.
/// Valid for PSPDFFreeTextAnnotation, PSPDFChoiceFormElement and PSPDF
@interface PSPDFAnnotation (Fonts) |
I'm also seeing anonymous categories incorrectly called out for being undocumented.
Both |
I'm seeing this as well. I made an extension of UIDevice, provided documentation on it, but it also is ignored when skipping undocumented items. |
…MarkNamesCursorInfo()` Their values are same with "key.nameoffset" and "key.namelength" in most case. When kind is extension, their values locate **the type's declaration** in their declared file. That may be different from the file declaring extension. So, using them is wrong. Is this related to realm/jazzy#454?
Any updates on this? |
It'd be useful to check to see if this is still an issue. |
I generated documentation last Wednesday. We have extensions for Date, UILabel, UIDevice, and UIViewController. All have the same level of documentation. Only the Date extension is showing up in our documentation. |
@JoshHrach is this with jazzy 0.7.3? What steps exactly could I follow to trigger this issue? |
Fixed in #819 |
I have an extension of NSDate in my project. It looks a little like this
Jazzy puts the NSDate extension into the documentation when generated but lists it as "Undocumented".
Not sure if I'm missing something obvious or of it's a bug.
The text was updated successfully, but these errors were encountered: