Kasper
our idea is that each package should have meta-data:
- default code formatting
- false positive for rules
- and of course package comment.
So for now the simplest thing we did was to add a class called
ManifestXXX for packageXXX.
This way it is versionned with the classes and we can browse it....
Stef
Le 4/5/15 18:33, Kasper Osterbye a écrit :
In the Nautilus browser I have been working a bit on allowing Pillar for
class comments. When browsing that part of Nautilus, I notice that there are
some hooks for package comments in the getComments and addComments methods.
Is there a history of "package comments" somewhere in the system? I was not
able to find anything like that. Also it does not seem like there are any
fields in the hierarchy of MBInfo that has anything to do with
documentation. Is that the case?
--
View this message in context:
http://forum.world.st/Package-comments-tp4824353.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
