Add 'number' as a body value type

[ariel-m-s]

Feature: Add 'number' as a body value type

Description

JSON does not define 'integer' and 'float' as valid data types, but rather merges them both into the 'number' data type. This PR includes 'number' as part of the data types, but does not remove 'integer' and 'float' for backward compatibility.

I think that 'array' and 'object' should also be allowed (somehow).

Requirements

None.

Additional changes

None.

[codecov-io]

Codecov Report

Merging #46 (32a0858) into master (b6ff279) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #46   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           14        14           
  Lines          200       200           
=========================================
  Hits           200       200           

Impacted Files	Coverage Δ
zum/requests/helpers.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b6ff279...32a0858. Read the comment docs.

[daleal]

Hi @ariel-m-s! When writing the description spec, I considered adding the number type, but I decided not to because it was completely redundant (in my opinion, the JSON format is wrong regarding the the merge of both types). Given that you can achieve the same result by using float, I still don't think it's a good idea to add that new type.
Regarding object and array, I don't think I'll add them either. For more complex structures, I think that allowing to pass a JSON file (or TOML or YAML, hopefully at some point) directly to the CLI is the better alternative. @sehnsucht13 was tackling that particular feature on #43, but I haven't heard from him for a while. I really haven't had the time to tackle that feature myself, but I'll wait for a while to see what @sehnsucht13 comes up with and, if he decides that he doesn't want to complete the feature, I'll add it on a PR for 0.3.0.

With all that being said, I'm going to close this Pull Request, as the type that you want to add is redundant.