So, it’s important to understand what the new inheritance system actually implies. There are two separate projects in play, after an upgrade:
global - where previously “global” resources lived. This defines a set of resources (including shared templates, etc)
<yourproject> - which inherits from the global project. Those inherited resources act as if they’re actually present in <yourproject> - but they cannot be edited, because they’re not actually there. If you want to make modifications, you have two options:
- Right click the ‘greyed out’ resource to override it. This creates a copy of the parent’s resource definition, only this copy is actually inside your project, meaning you can edit it. The downside to doing this often is that you aren’t changing things in a “global” way.
- Open the
globalproject and make your edits there. Then, the next time you pull in changes in<yourproject>, you’ll get an updated inherited resource. It’s still not actually in<yourproject>, but you can use it as if it was.
It’s a different way to think about inheritance from what we had before, but it’s incredibly more powerful and flexible.
I’ll make a note to have someone double check that template upgrading is working as expected, but so far it does appear that it is.