Skip to content
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

Support all ObjC documentation commands #368

Open
jessesquires opened this issue Nov 15, 2015 · 11 comments
Open

Support all ObjC documentation commands #368

jessesquires opened this issue Nov 15, 2015 · 11 comments

Comments

@jessesquires
Copy link
Contributor

jessesquires commented Nov 15, 2015

In testing the ObjC docs parsing (#367), I found that @discussion is not parsed.

However, @note does work, so this probably isn't high priority to fix.

I'm assuming this is because Swift supports - note:, but not - discussion:.

Screenshot of @discussion:

screen shot 2015-11-15 at 11 08 17 am

You can see @note working in this case in the final docs here.

@jpsim
Copy link
Collaborator

jpsim commented Nov 15, 2015

How would you expect @discussion to work? Same as @note? e.g. sidebar with DISCUSSION as mini-title?

Do you know if there's an exhaustive resource listing all the ObjC doc commands like Erica Sadun's reference for Swift?

@jpsim jpsim changed the title For ObjC docs, @discussion not parsed Support all ObjC documentation commands Nov 15, 2015
@jpsim
Copy link
Collaborator

jpsim commented Nov 15, 2015

This is the best reference I could find: http://stackoverflow.com/a/19169271/373262

I've updated this issue title to reflect adding support for all these commands.

@jessesquires
Copy link
Contributor Author

How would you expect @discussion to work? Same as @note?

👍 I think so.

After some more thought, I'm not completely convinced this is worth it. To me, note and discussion are basically synonyms. Maybe we should just document the accepted keywords? On the other hand, using @discussion is probably somewhat common.

Do you know if there's an exhaustive resource listing all the ObjC doc commands?

Also not sure how useful/valuable some of these other keywords are, or how frequently people would use them? Most valuable are probably @pre, @post, and @invariant. The others.... meh. 😒

@jpsim
Copy link
Collaborator

jpsim commented Nov 16, 2015

I think we should just support them all, unless you can think of valid reasons not to. It's pretty straightforward to do.

@nlutsenko
Copy link
Contributor

The most impactful one would be actually @deprecated, which might involve slightly more css work, since the default style is to cross out the declaration as well.

@shpakovski
Copy link

I'm trying to build documentation for an Objective-C project, but multiline @code-@endcode blocks are ignored by Jazzy.

Do you know any alternative supported by Xcode? It looks like Apple IDE does not recognize in.hand.m` files.

P. S. I also tried @verbatim-@endverbatim, \code-\endcode, and \verbatim-\endverbatim. No success.

UPD: I found 2 possible solutions and committed them into Jazzy and SourceKitten. Although I know they are lame 😊 So please consider to fix this stuff in a proper way. Thanks in advance!

@JanC
Copy link

JanC commented Aug 23, 2016

Hi,
I'm also looking for a way to include code snippets in the documentation. As mentioned the @code and @endcode do not work. When I use the markdown

``` ... ```

the generated jazzy html formats correctly the code but not Xcode when I option click on a method.

@pigeondotdev pigeondotdev self-assigned this Nov 23, 2016
@pigeondotdev
Copy link
Contributor

Any progress on this? I see @shpakovski's commits but not sure if they resolved this or were merged in. Would love an update. :)

@jpsim
Copy link
Collaborator

jpsim commented Nov 26, 2016

No, I think @shpakovski's commits were contained to that fork.

@melbic
Copy link

melbic commented Jan 25, 2017

I'm stuck with the @code problem as well. @shpakovski could you please create a pull request to merge your fix into jazzy?

@shpakovski
Copy link

@melbic I don’t think those fixes are good for production, so they are not worth PR. Sorry for the slow reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants