Issue #23072 has been reported by Jeremy Liberman.
----------------------------------------
Bug #23072: Puppet Gem modifies behavior of Class.to_yaml method
https://projects.puppetlabs.com/issues/23072
* Author: Jeremy Liberman
* Status: Unreviewed
* Priority: Normal
* Assignee:
* Category:
* Target version:
* Affected Puppet version: 3.3.1
* Keywords: puppet yaml irb
* Branch:
----------------------------------------
Can someone please explain this behavior? I couldn't find any features in the
Puppet documentation that would explain why something like this would be going
on. Looks like a bug:
<pre>
irb(main):001:0> class Foo; end
=> nil
irb(main):002:0> require 'yaml'
=> true
irb(main):003:0> Foo.to_yaml
=> "--- !ruby/class 'Foo'\n"
irb(main):004:0> require 'puppet'
=> true
irb(main):005:0> Foo.to_yaml
=> "--- !ruby/object:Class {}"
</pre>
The output of to_yaml changed because I added puppet? This breaks other gems
that serialize ruby classes to and from YAML.
Apologies if I didn't fill out this bug report correctly. This interface is a
bit... unwieldy.
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
