Maxime Mangel

**Comment by [MangelMaxime](https://github.com/MangelMaxime)** _Friday Aug 23, 2019 at 10:15 GMT_ ---- Hello, what's the JSON output of `.Net side` when applying the encoder to `[]`?

**Comment by [et1975](https://github.com/et1975)** _Friday Aug 23, 2019 at 12:31 GMT_ ---- Struct types retain the shape of their non-struct types, so currently it looks like any other DU: ```json ["AttributeId","00000000-0000-0000-0000-000000000000"]...

**Comment by [MangelMaxime](https://github.com/MangelMaxime)** _Friday Aug 23, 2019 at 19:23 GMT_ ---- Ok, so I need to do more test on my side because I don't see why it's not working...

**Comment by [et1975](https://github.com/et1975)** _Friday Aug 23, 2019 at 19:46 GMT_ ---- Probably better to have an option somewhere.

I need to check this option, but every library makes some choices about how to represents the type on JSON, so it's hard to have a standard way. Mainly, because...

Hello @davidtme, I don't know if you are using `inline` just for the demo or in your application too. But using inline, will indeed increase the bundle size each time...

Also, I am not sure if `Object.assign` will create a copy of the nested records or if this keep a reference to the original nested record. Like in case of:...

> @MangelMaxime the inline's and 30 field record is just to show how the problem can grow. I didn't want to post up a 200 line record with 200 updates...

Thank you for investigating. Feels a bit hacky ahah

With the unify parser we don't use `obj` anymore but a real JSON type.  With this real type the compiler is now able to help the user write encoders.