CODEWITHSUNDEEP
classmvvmviewmodelnaming
Buck
Buck

Reputation: 599

MVVM ViewModel Naming

I have the views named as actions such as "SelectMethod". Wondering, if it makes sense to name the associated view model as "SelectMethodViewModel" or should it not use the action (i.e. Select) in the naming? I am thinking classes should be things so does the action not make sense or am I over thinking this? I know this is a simple question, but it has a trickle effect in the application.

Upvotes: 2

Views: 476

Answers (2)

Marc
Marc

Reputation: 13194

SelectMethod is not a good name for a view. A method is not a class, but a view is a class and so a view is not a method. I would suggest:

SelectionView
SelectionViewModel

Upvotes: 1

eandersson
eandersson

Reputation: 26352

I would definitely go ahead and use the same name for your View and ViewModel. In fact I would take it one step further and add View to SelectMethod.

This basically ensures that we know the relationship and purpose of the two classes.

TestView
TestViewModel

Upvotes: 2

Related Questions