An effortless (on my part) suggestion: Better control over inheritance
Hi, I say effortless because I'm in no position to do it myself :-), & not sure where else to put a suggestion so ill chuck it here.
Would be great if we had better control over inherited datatypes, the way it is at the moment can really screw you over if you forget something early on, or put something in early on, then weeks down the line you apply a datatype to X and it trickles down and can ruin everything below it, if you didn't want it there.
I think a simple "don't trickle down" or "ignore parents" etc, flag would be great, at this point I'm scared of using the inheritance because I cant confidently say "is this how I want that forever?"
I'm guessing you mean docType inheritance ? How about using docType compositions instead ? (you can add / remove docType compositions from a docType at a later date should you need)
An effortless (on my part) suggestion: Better control over inheritance
Hi, I say effortless because I'm in no position to do it myself :-), & not sure where else to put a suggestion so ill chuck it here.
Would be great if we had better control over inherited datatypes, the way it is at the moment can really screw you over if you forget something early on, or put something in early on, then weeks down the line you apply a datatype to X and it trickles down and can ruin everything below it, if you didn't want it there.
I think a simple "don't trickle down" or "ignore parents" etc, flag would be great, at this point I'm scared of using the inheritance because I cant confidently say "is this how I want that forever?"
Thanks <3
Hi Kieron,
I'm guessing you mean docType inheritance ? How about using docType compositions instead ? (you can add / remove docType compositions from a docType at a later date should you need)
I love compositions... I just wish I could inject additional "parts" further up in the tree after I have started using them...
is working on a reply...