Protect against related field issue

[sposs]

Hopefully fixes #24

[vdboor]

Hi! Thanks for offering this fix. It looks like a good first start. I wonder, would it be possible to have some kind of unit test or example for this? That would make it easier to guarantee this is the right fix. TIA!

[sposs]

I've added a test that fails if the patch is not added. Moreover, I see that the previous test cases passed because the feature Restaurant has a field 'name' and the city also has a field 'name', and so there is collision between the field names. I've thus added a field that does not exist in the Restaurant to ensure the resolution of related.

[sposs]

Last commit needed because your pre-commit hooks are a little too strict on the line lengths...

[vdboor]

Sorry I missed this one, looks good! Thanks!

[vdboor]

I've merged this manually with rebasing (to resolve conflicts). Your changes are in 7294678 and are released as 1.4.1 :-)

I've updated our pre-commit-config too in main. It's quite odd that it triggered for you, as pre-commit run -a doesn't report anything here.