Two separate tables???

Hi Allen,

Congrats on great work on this component! I am just wondering why you decided on two separate tables for header and body? It sounds crazy to me to go that route! You have to spend so much effort to keep them aligned. I would have just had a single element with config and data parameters, like:

<BootstrapTable {...tableConfig} {...data} {...columns} /> This would generate a single table like:

<table class='table'>
  <thead>
  </thead>
  <tbody>
  </tbody>
</table>

Cheers

[tacomanator]

@AllenFang I may have misunderstood your point but in any case, where does something like this fall short: https://jsfiddle.net/0ho7dxy1/1/

[innopal]

I appreciate your attention to this fundamental issue @AllenFang and @tacomanator! I would say though that you really should not be worried about large number of columns. That to me is a design issue. A table/grid is for a limited number of columns that can be displayed in a sane fashion in a viewport. If there are more detailed data that is directly related to the entity that is represented in a row, you could either provide a link or maybe even implement an expandable row that can be a custom component and people can put whatever they want in that custom component. There seems to be a discussion already about expandable row here: [https://github.com/AllenFang/react-bootstrap-table/issues/362]

If you are trying to build a spreadsheet component then that’s a different story. In which case I would suggest a cell-based approach instead something similar to https://handsontable.com/

Cheers