React-bootstrap-table2: Impossible to use data with dots in the keys

[avindra]

If I push some data to the table that has dots in the response, for example

{ "data.entity" : 7, "attribute.name" : "Physical" }

The table is unable to handle the data. I think there is a feature that uses dots somehow, but that should not prevent being able to pass in this kind of data.

Otherwise, people are having to write transformations, like removing the dots, which breaks integrity of data across your app, and causes the need for inane mappings.

Here is a code sandbox that replicates the problem:

https://codesandbox.io/s/xenodochial-faraday-t7y2v?file=/src/App.js

[allez-allez-allez]

I am having the same use case. For example with the following results returned from an elastic search query:

{
    "highlight":{
        "exploitation_requirement.iee":[
            "akasdhfklashfsklajdf",
            "sdfsdf"
        ]
    }
}

I was expecting to retrieve the dataField using the following column definition:

{
    "dataField":"highlight.exploitation_requirement\\.iee",
    "text":"exploitation"
}

I believe this functionality exists from the traditional datatable plugin as referenced here: https://datatables.net/forums/discussion/29299/bug-error-while-loading-object-with-a-dot-in-the-associative-array-key and http://live.datatables.net/qupodefa/1/edit

This library has been working great for me and my organization. I hope someone can take a look at this.

[AllenFang]

Thanks @allez-allez-allez So far I didn't hear any bug about dot is not work. So @avindra please give me an online example on codesandbox so that I can help u. thanks!

[avindra]

@AllenFang here is a code sandbox replicating the issue and also includes a common workaround (that we are trying to avoid because it involves re-copying data across objects):

https://codesandbox.io/s/xenodochial-faraday-t7y2v?file=/src/App.js

Please re-open the issue.

[avindra]

@AllenFang I should also mention, this issue is not present in the deprecated version 1 library.

So I guess it was introduced some time after the release of version 2.