Jira (FACT-166) fact names should be limited to a single type

[Adrien Thebo (JIRA)]

Title: Message Title

Adrien Thebo commented on an issue   Re: fact names should be limited to a single type After talking with Andy we came to the conclusion that this is mainly the result of not having a separation of the Facter DSL and API. To really solve this we need to decouple the two and make the DSL handle these conversions so that the API doesn't have to handle the conversions. However this isn't a blocker for Facter 2 and it would take more time than we really can spare. I'm removing this issue from the sprint and untargeting this issue from the Facter 2.0 release. Add Comment   Facter / FACT-166 fact names should be limited to a single type Facter currently allows the usage of both Strings and Symbols types as fact names. In a number of places the "names" get silently converted to lowercase symbols but this conversion is somewhat inconsistently done. Per discussion with Abrien Thebo, we've agreed that fact names should be officially restricted to lowercase Symbols only. As a compatibili... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.