Closed bsrikan closed 6 years ago
I think your working copy of valid-ref-2 is not on github yet? I'd like to examine it, as it seemed like other similar model descriptors were working OK.
Attached those models herewith. e2e_ns_Models.zip
thanks ill check them out.
OK -- not a bug.
I found where in the code I am neglecting to include path range indexes for namespaces. Turns out behavior is correct.
If there are element range indexes, then the namespace information is included right in the element-range-index block. It doesn't need an entry in path-namespaces to resolve it.
So for those types with element-range-index, but not a path-index, there will be no path-namespace definition.
Back to you for verification
Agree with dev comments. Shipping the issue as not a bug.
Model valid-ref.json in e2e has 2 namespaces with prefix 'cust' and 'ord' but only one is generated in database-properties-generate()