Orphan documents

Deleting a user who is the owner of documents causes 500 internal server error on project pages, could be the same for tags.

- Add a new ```UserNullable``` concern to be include in any association between and user and that particular entity; the concern will return a ```NullUser``` if a nil one is set.

https://www.pivotaltracker.com/n/projects/982890/stories/66066822
I don't think this will bring any headache in the future, we can use
something like naught to mimic functionality from another class and create
it as a nullable class; without bringing the entire AR models into it. Also
removing the inheritance from this class won't cause any harm.


On 27 August 2014 13:32, Bryan Yap <notifications@github.com> wrote:

> In app/models/null_user.rb:
>
> > @@ -1,11 +1,11 @@
> >  class NullUser < User
>
> well the NullUser should behave exactly like a normal User, the easiest
> way to achieve this is to subclass the model itself. But maybe you are
> right, we don't need all that functionality at the moment, although it
> doesn't hurt and saves us from headaches in the future.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/AgileVentures/WebsiteOne/pull/513/files#r16791071>.
>



-- 
Rafael George