| 1 | | If we were able to do it over again, I'd try much harder to avoid swappable models. At this point, they've been a feature for long enough that we're going to have a really hard time getting rid of it. Major libraries are using it, such as waffle. Unless we're so solidly against it that we're going to start actively discouraging using this feature, I think it's time that we buck up and document and support this feature of our authentication system. Either get rid of it (excepting backward compatibility concerns) or support it fully, continuing this limbo state is bad for everyone. |
| | 1 | If we were able to do it over again, I'd try much harder to avoid swappable models. At this point, they've been a feature for long enough that we're going to have a really hard time getting rid of it. Major libraries are using it, such as waffle. Unless we're so solidly against it that we're going to start actively discouraging using this feature, I think it's time that we buck up and document and support this feature of our ORM. Either get rid of it (excepting backward compatibility concerns) or support it fully, continuing this limbo state is bad for everyone. |