Native inheritance in blueprints
James Daniels
We have multiple different types of component . Currently we either need to model them as entirely separate blueprints or we try to merge them into one common shared blueprint. The latter has proven to be a bit unwieldy, when differences arise between types they tend to bleed through in the Port UI in certain places making the UX for the user a bit confusing.
J
James Daniels
Thanks Maria for raising this on my behalf. The additional context to add here is...
If we could have a parent blueprint called "components" (base class) where you don't actually registry new entities but instead you create inherited child blueprints from the base. The children can then add additional fields specific to them, but the common ones are jointly available. From a blueprint-to-blueprint relationship point of view you then only need to manage relations to the base class and all the children get that relation flow too.