I find it inconsistent to have it for some public methods and not for others. I guess you could add a (!) depending on the context: // function to get the

I find it inconsistent to have it for some public methods and not for others. I guess you could add a (!) depending on the context: // function to get the recipes (!) function getRecipes() Or just document what recipes actually mean within the application context.