Master Detail class name convention about ios-handbook

[kostiakoval]

Hi, can I add my comments here? 👍 for the renaming, I agree that the s letter is not enough to differentiate the components.
Another solution could be RecipesController and RecipeDetailController

[elland]

@3lvis Not really that fond of calling things lists.

@kostiakoval I like that. Simple and just as verbose as we need to, without having to identify it visually as a list, collection, grid, etc.

[marijnschilling]

Yes I agree, I think RecipesController and RecipeDetailController will do the trick

[3lvis]

[3lvis]

@elland reasoning against using RecipeListController?

[elland]

@3lvis it's on my very first comment. 🤔

[marijnschilling]

I think List is confubsing, because it can either be a list or a collection of items. I think just using a plural is more accurate in this case.

[elland]

Yeah, keeping how the UI is presented out of the controller name sounds good to me. No need to rename if the presentation changes etc.

[3lvis]

@elland I was asking for extra clarification, "I'm not very fond" didn't seem like a proper argument. @marijnschilling's answer was great, though. I think it clarifies what you meant.

[elland]

@3lvis your answer feels like you didn't read my whole comment.

Simple and just as verbose as we need to, without having to identify it visually as a list, collection, grid, etc.

[3lvis]

Doing some spring cleaning, please make a new issue if you still want to do this.