Issue #11076 has been updated by Brice Figureau.
Nigel Kersten wrote: > It feels like we could do with something to namespace them with Puppet Labs > and some initials to represent the product. > > e.g. Facter could have > > PLFR0102 > > Puppet could have > > PLPP0103 > > etc. > > but those are horribly staid. :( I guess you're now ready to port Puppet on VMS :-D ---------------------------------------- Feature #11076: Error messages should all have a unique identifier https://projects.puppetlabs.com/issues/11076 Author: Nigel Kersten Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: It's difficult to search for phrases when trying to work out what has provoked a given error message. Something IBM did quite awesomely was to have unique identifiers for their error messages so that you could more easily search for information on them. I'm not suggesting we abandon providing a human-readable phrase explaining the error in context, but that we instead append a unique identifier of some kind so that we can more easily provide significantly more detail in our documentation around errors. Love to get feedback on this idea, particularly from docs and UX. -- 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://projects.puppetlabs.com/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.
