Type collision when extending a parent type or when the same variables are used. about tsoa

[github-actions]

Hello there TrevorDMartin 👋

Thank you for opening your very first issue in this project.

We will try to get back to you as soon as we can.👀

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

[RayJSeth-kr]

If two different endpoints define the same variable for a type only one type is represented in the schema.

I know this was the secondary issue described here, but this is the issue giving me the runaround today.
Hypothetical example that follows the structure of what I'm trying to accomplish:

Upon further reading of the initial issue, the whole description is actually what I'm experiencing so I'll truncate my initial restating of the problem.

My thoughts on some potential solutions:

• just roll a simple iterator when collision happens CollidingType_{n} for all collisions
  • feels like conceptually the wrong solution, more like a workaround that might result in bad side-effects
• hash/obfuscate the resolved module path and prefix type with it
  • more closely aligns tsoa to how TS handles this sort of same name resolution
  • however, pretty complex approach

Ultimately I think if I had been presented with a warning or error that the collision occurred, just that would have been acceptable. Changing the variable name for the type was trivial, but it was trying to find out where the erasure of the second type was coming from that took time.
Any chance of a config option to opt into a 'strict no collisions' mode?