Inherit Type from Content or Default
For *content settings, the actual setting card is used for the content, so this already is the case, but for *default settings, created cardtypes should use the type of the *default setting for the Card::<class> to inherit from, rather that alway inheriting from Card::Basic
Related support tickets:Relevant user stories:add oneTags:
There is more to type inheritance than just the content, and I think even in the case of *content we're not inheriting in all the ways we'd like. flags like collection? and clean_html? for example. It really gets tricky when we start thinking of not just code inheritance but setting inheritance :)
Hmm, I definitely see your point. But should we do this now anyway whether or not we can handle the more tricky cases?
I think that when we fully implement features like collection? and clean_html?, this ruby level inheritance should pick up all the necessary hooks to inherit these features as well. You are right that settings are tricky, but if we really want that, the general solution that has setting lookup integrated with Card::* method inheritance. That is beyond the scope of this card.
--Gerry Gleason.....Thu Feb 17 14:31:45 -0800 2011
gerry, yes I'd say let's do the ruby inheritance and not worry about set ramifications for now.
--Ethan McCutchen.....Fri Feb 18 10:45:38 -0800 2011
Notes