Resolve circulair includes

[friedelschoen]

By definition XSD does allow circulair includes, but trying to do so results in a "hot-potato" loop. This fix holds a loaded schema in memory which won't be re-resolved over and over.

Example of such case: https://github.com/BISONNL/NeTEx-NL

netex-nl-enum.xsd <=> netex-nl-basic.xsd

[friedelschoen]

When merging circulair dependencies, types will be re-added to the schema, this fix merged and deduplicate things.

[friedelschoen]

P.S. NeTEx also has a name-clash coming from case-sensitivity:

<xsd:element name="FlexibleServiceProperties" type="flexibleServiceProperties" maxOccurs="unbounded"/>

GoName() turns both names to FlexibleServiceProperties, my quick-fix is to append 'Element' in Element.GoName(). This is a specific problem to NeTEx, is a pull-request desirable?

[isimluk]

Thank You for your contribution, @friedelschoen . Don't worry about the lint.

Let me find some time later to review this in depth.

In the mean time, would you perhaps like to add a minimalist test for this?

[isimluk]

GoName() turns both names to FlexibleServiceProperties, my quick-fix is to append 'Element' in Element.GoName(). This is a specific problem to NeTEx, is a pull-request desirable?

There is an open semi-abandoned pr #45, to rework name clash resolver. You can take a look to see whether you like that path.

[friedelschoen]

I'll add some tests next week 😄

I want to look into #45 as NeTEx has many such shenanigans but cannot promise anything.

[friedelschoen]

Hey! I've added some short unit tests for circular includes and imports, is that alright?