Is it good to have MVVM without a model for temporary things?

Question

Do you think it's architecturally normal to use ViewModel - a modelless view for temporary things?

For example: I want users to enter some paths so that later I can open some files. It makes no sense for me to store the paths anywhere, only the ViewModel, and when the user clicks "Show all files", I then create file models and ViewModels for the View that somehow represent them. So actually my only model is the file model.

Answer 1

, , . , . , .

, , View Model View, , . , . , .

, , . , . , .

Answer 2

. -, .
, , , .

Answer 3

Of course. It makes no sense to move the logic of opening the file to a separate object so that you can say that you did it.