Open nlips opened 5 years ago
This is somewhat related to #15, will need to be implemented.
I think that fixing this bug will come from fixing issue #15. If xml-complete can clearly distinguish the contexts, it will no longer have difficulty pointing to the right element definition.
I have made that to a "fork" that might get adopted.. it looks back in parent and resolves by that context as long as they (the parent) have different names (like your sample).. if names are the same but tree different - it will show shared list
My schema contains two element definitions
<Property>
. Each one is valid in a specific context and have not the same attribute set (see attached file).<Property>
in<ElementA>
must have aIdentifier
attribute.<Property>
in<ElementB>
must have aName
attribute.Identifier
andName
attributes are suggested by xml-complete for the<Property>
element in<ElementA>
.