Haxe

yes https://haxe.org/blog/haxe-4.1.0-release/

So that's the  side effect I couldn't grasp 😉

yeah, should be easy to have this only for haxe 4.1, also i think im going to do it on the parser level (rather than the macro level) so that <import /> shows the right file

```
XMLParser.hx:21: characters 12-17 : Uncaught exception while parsing "sub-nested.xml": haxe.xml.XmlParserException: Duplicate attribute [style] at line 2 char 20
ComponentMacros.hx:115: characters 30-142 : Called from here
ComponentMacros.hx:87: characters 8-104 : Called from here
```

(sub-nested.xml is three levels deep fyi)

do you mean you can't import resource more than 3 level deep ?

no, i mean, i imported 3 levels deep so that i could make sure the right .xml file was being returned in the error... so yeah, for error reporting 🙂

hmmm pull and testing. Works superb ! (and it caught error in xml @ 5levels deep so I am not sure I get the 3 levels 😉

no no, basically, i was just saying that i tested that the exception showed the right file with with 3-levels of imports...

Thanks a lot this is a (bad coder) life saver !

so essentially:

> For error reporting you mean ?
yes. 😄

This omitRoot and exception catching will make it easy thanks again

no worries, both useful additions... i dont use imports much, but better error handling is certainly always a plus... ... and ill almost certainly use the omitRoot often

should have added omitRoot before rather than being lazy... it was a 10 second fix

what could this be? only happens occasionally it seems which is strange

oh - did you happen to put a buildComponent macro some place b4 the Toolkit was initialized?

took me quite a few hours before I realized that