Jon P

Thanks for the super fast reply @nirinchev - ok well was worth the ask, will solve with application logic. Have a good rest of week!

Any movement on this?

ooo that sounds amazing @nielsenko - ok will keep an eye on this and thanks for the heads up. This LINQ does not help the use case in this issue...

> I put up https://github.com/realm/realm-dart/pull/1078 - it doesn't cover all the requirements of this issue, but it makes it possible to use the model name rather than the mapTo-name when...

>We could also generate a type specific schema class. Then something like Fellow.schema.firstName.name would be possible. Could still allow Fellow.schema.properties['firstName'].name as well @nielsenko this would be perfect ;-) (both `Fellow.schema.firstName.name`...

Great to see https://github.com/realm/realm-dart/pull/1078 merged, thank you all. Will look forward to your further thoughts.

We have the same problem. +1 for this. If Realm is not compatible for a target OS/platform (i.e. web in this case) Realm should not block compiling... Flutter is a...

Thanks for this @rdunlocked18, unfortunately this approach will not work for us as our Realm Models are used throughout the application left right and centre. I suppose for more simple...

Hey @nirinchev hope you are well? Unmanaged objects would be amazing, and yes we would just call different functions for web (using our API instead of MongoDB Device Sync). So...

Just checking in to see if there has been any progress on this?