Sergio Pedri

So, there is one big elephant in the room here: **not all attributes are valid on both fields and properties**. We need to remind ourselves that what we're doing today...

Yes, that is what made me not do this in the first place. I do have many issues with this. As I said, I really don't see a "perfect" solution...

I really don't like `AttributeDecorator` though, as it would completely kill the build-time safety of using other attributes and passing parametrs to it. As in, we'd have to essentially reimplement...

Honestly I'm thinking the only proper way would be to have opt-in forwarded attributes, like: ```csharp [ObservableProperty] [SomeAttribute] [SomeOtherAttribute] [AlsoForwardAttribute(typeof(SomeAttribute))] // opt-in private string name; ``` This would instruct the...

This is now superseded by #413, closing this one.

Leaving an update here as @brminnick asked - right now the 8.0 release is feature complete and I'm just working on stabilizing stuff and fixing last minute bugs. I'm happy...

Those labels were just leftovers from when the issue was moved to this repo, but they have no meaning here. I've removed them 🙂

With respect to these two: > - We did not find a way to validate and show visual feedback on the fields to the user when clicking submit button (for...

Thanks @mvegaca for the small repro, I'll take a look! Also curious to see if I can repro that on UWP, to check whether that issue is specifically related to...

Tried to run the sample, and that didn't work for me either. Attached the local MVVM Toolkit package so that I could step into it, looks like the call to...