close fullscreen

So, this gets rid of the account "extension"?

 

And is dependent on implement triggers?

related to Refactor Out Admin and Account Controllers ?

--John Abbe.....2013-05-06 03:14:48 +0000

definitely related. could fuse. this is the better name, but there's more info on the other one (and the "admin" thing isn't so related). probably not worth cleanup yet...

--Ethan McCutchen.....2013-05-06 03:44:34 +0000

fyi that one's tagged 1.13 (didn't see it at first, cf handle truncated content in labeled view better)

--John Abbe.....2013-05-06 03:55:02 +0000

yeah, I think that was intentional but probably makes less sense now. will change this one. really need to focus on the action api stuff before digging further into this overhaul.

--Ethan McCutchen.....2013-05-06 03:59:06 +0000

We don't really have "extensions" in the old sense anymore. User model is the one remaining exception. We have a base card for this now, the +*account (codename :account) trait. The last part is moving the data accessed in the User model into cards. They will be plussed onto the +*account card, and we are planning a way where for specific traits of the :account trait (:email => *email for example) would look on the +*account card for a plus card first, then search to the parent (left) card.

--Gerry Gleason.....2013-06-11 15:58:38 +0000