A BigDecimal would be naturally represented as a JSON number. Most libraries, however, parse non-integer JSON numbers directly as floats. Clients using those libraries would get in general a wrong number and no way to recover other than manually inspecting the string with the JSON code itself.
That’s why a JSON string is returned. The JSON literal is not numeric, but if the other end knows by contract that the data is supposed to be a BigDecimal, it still has the chance to post-process the string and get the real value.
# File lib/active_support/json/encoding.rb, line 198 198: def as_json(options = nil) to_s end
# File lib/active_support/core_ext/object/duplicable.rb, line 113 113: def duplicable? 114: true 115: end
# File lib/active_support/core_ext/big_decimal/conversions.rb, line 27 27: def encode_with(coder) 28: string = to_s 29: coder.represent_scalar(nil, YAML_MAPPING[string] || string) 30: end
# File lib/active_support/core_ext/big_decimal/conversions.rb, line 34 34: def to_d 35: self 36: end
# File lib/active_support/core_ext/big_decimal/conversions.rb, line 40 40: def to_formatted_s(format = DEFAULT_STRING_FORMAT) 41: _original_to_s(format) 42: end
This emits the number without any scientific notation. This is better than self.to_f.to_s since it doesn’t lose precision.
Note that reconstituting YAML floats to native floats may lose precision.
# File lib/active_support/core_ext/big_decimal/conversions.rb, line 18 18: def to_yaml(opts = {}) 19: return super if defined?(YAML::ENGINE) && !YAML::ENGINE.syck? 20: 21: YAML.quick_emit(nil, opts) do |out| 22: string = to_s 23: out.scalar(YAML_TAG, YAML_MAPPING[string] || string, :plain) 24: end 25: end
Disabled; run with --debug to generate this.
Generated with the Darkfish Rdoc Generator 1.1.6.