Why is NoticeType not just a simple Enum?

[lggwettmann]

Hey guys,

loving the idea of the package so far. I found the installation steps for the NoticeTypes quite interesting, though. I'd be curious to learn why you choose for saving the NoticeTypes in the DB while there is a need to hardcode them in the rest of the code?

Why did you not go for a simple Enum or object which a) doesn't need DB access b) is much easier to set up?

I'd be happy to provide a pull-request in case this is something you were contemplating. I understand that this could mean a breaking change with a new version of pinax-notifications.

[KatherineMichel]

I don't know why the original authors didn't use enum. The choice goes back quite a few years (to 2008?). I think @jtauber and @brosner were involved. I don't know if they'd want to change to enum at this point or not. https://github.com/jtauber-archive/django-notification/tree/old-master

[lggwettmann]

Thanks for your answer, @KatherineMichel.