Issue #2364 has been updated by Brice Figureau.

Status changed from Accepted to Ready for Testing
Target version set to 0.25.0
Complexity changed from Unknown to Medium

The code is pending review, and is available in my github repository branch: 
tickets/master/2366:
http://github.com/masterzen/puppet/tree/tickets/master/2366
----------------------------------------
Bug #2364: No puppetdoc for subclass not preceded by resource or another 
subclass
http://projects.reductivelabs.com/issues/2364

Author: Alan Harder
Status: Ready for Testing
Priority: Normal
Assigned to: Brice Figureau
Category: documentation
Target version: 0.25.0
Complexity: Medium
Affected version: 0.24.8
Keywords: puppetdoc


Using 0.24.8 on Solaris 10.
Consider this modules/test/manifests/init.pp:
<pre>
# Test class
class test {
  # Test subclass
  class subclass {
  }
}
</pre>

puppetdoc (rdoc mode) includes both "Test class" and "Test subclass" comments 
in the appropriate places.  However, this code:
<pre>
# Test class
class test {
  $foo = 1

  # Test subclass
  class subclass {
  }
}
</pre>
This time puppetdoc does not include "Test subclass" in the page for 
test::subclass.

With some experimentation I found that the preceding comment for a subclass 
does get parsed if the code before it is a } that ends a resource or another 
subclass.  Other code (like the assignment above, or even a } ending an "if" 
block) will cause the subclass doc block to be missed.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to