Type hierarchy 2

[marcofavorito]

Proposed changes

This is a sub-PR to #73 to add changes in a more trackable way.

• Commit 842890a adds a test provided in Not parsing the type hierarchy #70 that defines the expected behaviour of the new type parsing feature, the main topic of PR Fix/type hierarchy #73.

Fixes

n/a

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply.

• I have read the CONTRIBUTING doc
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works

Further comments

n/a

[francescofuggitti]

Thank you!

[codecov-commenter]

Codecov Report

Merging #75 (6c47b9f) into fix/type_hierarchy (9d195b0) will not change coverage.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@                 Coverage Diff                 @@
##           fix/type_hierarchy      #75   +/-   ##
===================================================
  Coverage               88.62%   88.62%           
===================================================
  Files                      20       20           
  Lines                    1064     1064           
  Branches                  169      169           
===================================================
  Hits                      943      943           
  Misses                     94       94           
  Partials                   27       27           

Flag	Coverage Δ
unittests	88.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[marcofavorito]

@francescofuggitti should we enforce the presence of "object": None? That is, the types dictionary should contain as keys all the root nodes (or leaves nodes, depending on how we see the inheritance relationship).

[marcofavorito]

continuing on main PR