Add Dash table

[mr-m-coetzee]

Add converted dash_table component.

Note: Changed JSON serializer's configuration to use default naming standard.

Using camel-case naming forces DataTable (and probably everything else) to only work with data with camel-case field names. I.e. {| State = "online" |} does not work.

[kMutagene]

LGTM overall, but this really highlights that tests are desperately needed, especially for serialization. I would suggest we use the same strategy for serialization everywhere (JsonProperty vs anonymous records) though. Also, is the DashApp still correctly serialized with this setting?

[kMutagene]

If we want to stop using the camelCase serializer settings, we should add JsonProperty attributes (like here) to all records that will not get serialized correctly with the new settings. Another example (which is why we used camelCase serialization can be seen here)

[mr-m-coetzee]

Good point - that would be clearer.

[mr-m-coetzee]

Just to make sure we're on the same page: The problem with the camel-case field names is with "external" data, i.e. when it is being used to pass data in, e.g.

DataTable.dataTable "memory-table" [
    DataTable.Attr.data [
        {| Country = "Canada" |}
        {| Country = "USA" |}
    ]
]

Country would be camel-cased and would fail to bind correctly to the header record "Country".

[mr-m-coetzee]

Also, is the DashApp still correctly serialized with this setting?

Yes - As far as I can tell. Tested using Giraffe and Suave

[mr-m-coetzee]

I would suggest we use the same strategy for serialization everywhere (JsonProperty vs anonymous records) though

I'll add it to DashTable - but what about the rest? Do we want a separate Issue + PR for adding JsonProperty where anonymous records are currently being used?

[mr-m-coetzee]

If issue !29 gets the go-ahead, updating to JsonProperty can be done as part of that?

[kMutagene]

I would suggest merging this with json properties for now, and handling #29 in a separate PR. looks like going for the DynamicObj approach is the better way than using records at all for these objects anyways (see my comment on #29)

[mr-m-coetzee]

Updated with JSON attributes