Why `testTag` is part of the semantics tree? Why it’s not a separate entity?

# compose

[theapache64]

Why testTag is part of the semantics tree? Why it’s not a separate entity?

[andylamax]

Been asking myself this for a while too. It feels wrong for this to be part of production code

[theapache64]

I am fine with testTag in production. My concern is only around testTag being part of the semantics tree.

[theapache64]

Anyone can call clearAndSetSemantics from top layer for some a11y support and that may destroy the testTag, in turn break tests.

[theapache64]

@andylamax can you elaborate the problem u faced of having testTag in production?

[andylamax]

Well for me, its not really a problem perse (found none at all), its just that. We have main source sets and test source sets for a reason. if we start putting test information into our main source sets, the line of distinction becomes blurrier between the two

[theapache64]

Got it

[theapache64]

I think my problem can be fixed by using the flag useUnmergedTree 🙂