v1.2 Planning

[AAAYaKo]

Can be included in v1.2

• [ ] Rewrite ViewModel to ScriptableObject
• [ ] Rewrite Converter to ScriptableObject
• [ ] Implement ConvertBack
• [ ] Improve UX of DataBinding
• [ ] Improve EventBindings

[push-pop]

@AAAYaKo

So a few things to think about...

It is important (to me and probably other users) not to make breaking changes in between minor changes (1.1->1.2, etc...).

I am personally using this library in production projects for multiple clients but would like to take advantage of new feature Or if we do to have some kind of easy way to upgrade.

For example when I switched to OneWay/TwoWay bindings to just a single script, I added a deprecated warning on the old scripts and created a utility to convert the old way to the new way in a scene.

So for example if we change the UX of DataBinding, it is important that a project upgraded from 1.1 will still work.

On this list the ones that give me pause are rewriting ViewModel/Converter as ScriptableObjects. I'm curious what you see as the benefit of doing this vs how it already is.

I have made individual issues for these ideas so that we can track them seperately. Please use the individual issues for discussion and we can use this to discuss features/fixes as a whole.

Thanks!

[push-pop]

1.2 Issues:

https://github.com/push-pop/Unity-MVVM/issues/67

https://github.com/push-pop/Unity-MVVM/issues/68

https://github.com/push-pop/Unity-MVVM/issues/69

https://github.com/push-pop/Unity-MVVM/issues/69