Support nested custom schemas for models about forest-express-mongoose

[mcaldas]

Sure will do

…

On Wed, 30 Aug 2017 at 1:31 Arnaud Besnier ***@***.***> wrote: @mcaldas <https://github.com/mcaldas>, you are right on both points. Can you create an issue for each comment? We'll try to prioritise the fixes for next week. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADxcw5cQpmEl5bJNLq4IgN7byvyyKp8Oks5sdJEygaJpZM4PCoQV> .

[mcaldas]

@arnaudbesnier just created the 2 issues: #78 #79

[arnaudbesnier]

@mcaldas Thanks for the feedback!

We definitely need to work on this.
We might plan it for the next sprint.

[mcaldas]

@arnaudbesnier great!
When is your next sprint? :)

[arnaudbesnier]

Next week ;)

[mcaldas]

Great!

[arnaudbesnier]

The support is available on the latest liana version 1.2.3.

Thanks again!
Let us know if it does not work as expected.

🌲🌲🌲

[mcaldas]

@arnaudbesnier seems to be working thank you!
I realized that composite mongoose types aren't serialized either, for example mongoose.Schema.Types.Point
Is that a different issue?

[mcaldas]

@arnaudbesnier another issue is that on list view i see something like <client@model:forest-users-someschema::ember5328:owner(XXXXXXXX)>
Is that the expected behavior?

[arnaudbesnier]

@mcaldas, you are right on both points. Can you create an issue for each comment?
We'll try to prioritise the fixes for next week.

[aharon-vish]

Hi,
For me, it's doesn't work.
When I turn the field to mongoose.Schema.Types.Mixed the field in forest admin is disappear.