Why extra nesting level with Contents? #70

Open

Open

Why extra nesting level with Contents?#70

In https://github.com/codeclimate/platform/blob/master/spec/analyzers/SPEC.md#contents Contents field is a hash with a single body key. Why? Why not just make it a string?

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests