I actually like the Somethingable convention of naming modules, because for me it is natural to think of modules in terms of what they allow the including object to do.
I do however dislike trying to name modules according to the Somethingable pattern, but I wonder if that's just a failure of my vocabulary.
Awarable is very clunky, though. Is the point that when included in an object, you can... make that object aware of something? Off the top of my head, I would have gone with Alertable, Notifiable or something. Something that, even if you don't like the naming convention, is actually recognisable as a word.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I actually like the
Somethingableconvention of naming modules, because for me it is natural to think of modules in terms of what they allow the including object to do.I do however dislike trying to name modules according to the
Somethingablepattern, but I wonder if that's just a failure of my vocabulary.Awarableis very clunky, though. Is the point that when included in an object, you can... make that object aware of something? Off the top of my head, I would have gone withAlertable,Notifiableor something. Something that, even if you don't like the naming convention, is actually recognisable as a word.