API dox: Add @class comment with CamelCase include, image title without KDE
ClosedPublic

Authored by kossebau on Jan 15 2017, 12:55 AM.

Diff Detail

Repository
R236 KWidgetsAddons
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
kossebau updated this revision to Diff 10171.Jan 15 2017, 12:55 AM
kossebau retitled this revision from to API dox: Add @class comment with CamelCase include, image title without KDE.
kossebau added a reviewer: Frameworks.
Restricted Application added a project: Frameworks. · View Herald TranscriptJan 15 2017, 12:55 AM
cfeck added inline comments.
src/kselector.h
128

Does probably need a separate @class entry?

kossebau added inline comments.Jan 15 2017, 1:59 PM
src/kselector.h
128

Yes, but... :) There are a few headers which export multiple classes, like this one, but there are no matching CamelCase forward headers yet generated. I was to do this in a separate commit, to not put too much into this one (fixing the image titles already should ideally be a separate commit as well, are another matter).

kossebau updated this revision to Diff 10189.Jan 15 2017, 5:32 PM

add @class comments also for all classes in multi-class headers

kossebau removed a subscriber: class.Jan 15 2017, 5:37 PM

https://phabricator.kde.org/D4144 now would create the missing forward headers.

Only issue might be that there is no @since note possible... so people might start using the forward header without knowing in which KF version this forward header was added... possibly something that would need to be catched on the build front ideally, by somehow telling the header which min version of KF is assumed. Still would be nice to give a hint already in the docs. Any idea?

cfeck added a comment.Jan 16 2017, 1:24 AM

I would just add the missing forwarding headers without mentioning the version they first appeared in. Let's assume it is just a bug fix, and we do not mention bug fixes in the documentation.

cfeck accepted this revision.Jan 16 2017, 1:25 AM
cfeck added a reviewer: cfeck.
This revision is now accepted and ready to land.Jan 16 2017, 1:25 AM

Not perfect, but guess that is all we can do with current buildsystems, okay.
Could you also officially accept D4144 then? :)
Would wait for further feedback until the upcoming WE, and then push both unless someone objects.

This revision was automatically updated to reflect the committed changes.