Hi UnknownJ, Thanks for your great reply, it is exprimily helpful for me since I am new to TIQ. All the options that you have mentioned are essentialy good in their own ways, but might not produce the desired outcome for all types of teams though, but that is also what you say in the end of your comment. I personally very much like the github/JS/Extension approach. However, one of our key objectives is to simplify our TIQ setup, and one of the ways to do it in our case is to reduce JS complexity, so that less tech savy team members and stakeholders can also deliver in an efficient way. And for the same reason, I believe that creating a custom sollution for library inheritance might not solve our core challenges. We are currently working on consolidating out multi-profile setup into just few profiles. This might be a good opportunity for us to re-think our libraries and the need for them. But that would be a tough decision, since libraries have quite few advantages such as separation of concerns, inheritance etc.
... View more