Issue #1667 has been updated by luke. Status changed from Unreviewed to Needs design decision
All of the values in the documentation are generated directly from the Ruby values, and the text you're seeing is the text form of the regexes from Ruby. The only real way to fix this is to provide both a text and code form of the regexes, and I think that might be a bit much. Anyone know of a good way to get the correct text form of the regex? If not, anyone have a good way to fix this? ---------------------------------------- Feature #1667: Documentation should specify natural language regexs, not Regexp objects http://projects.reductivelabs.com/issues/show/1667 Author: ohookins Status: Needs design decision Priority: Normal Assigned to: Category: documentation Target version: Complexity: Unknown Affected version: 0.24.5 Keywords: Given it's not a necessity to be a Ruby programmer to use Puppet (or at least, it shouldn't be) I believe specifying standard regular expression notation rather than Ruby Regexp objects would be more straightforward. For example: <pre> Values can also match (?-mix:^[0-9]+$) </pre> this would make more sense if it were expressed as follows: <pre> Values can also match ^[0-9]+$ </pre> Even using the Regexp object .inspect rather than .to_s would produce a more generally recognisable representation of the Regexp object. ---------------------------------------- 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 -~----------~----~----~----~------~----~------~--~---
