Coverage increased (+0.08%) to 76.715% when pulling 9107a9a on joshleblanc:custom-table-body into f0ea9e5 on gregnb:master.

The same can be accomplished (visually) by providing a loader (custom ect.) Right before <MUIDataTable/>

Quick dirty example using the serverside pagination example, as an example.

const loadingComponent = (
      <div style={{position: 'absolute', zIndex: 110, top: 0, left: 0, width: '100%', height: '100%', display: 'flex', justifyContent: 'center', alignItems: 'center', background: 'rgba(255,255,255,0.8)'}}>
        <CircularProgress size={24} />
      </div>
    );

    return (
      <div style={{position:'relative'}}>
        {isLoading && loadingComponent}
        <MUIDataTable title={<Typography variant="title">
          ACME Employee list
          </Typography>
          } data={data} columns={columns} options={options} />
      </div>
    );

This isn't a feature that I think should be supported at this time. It has come up a few times (Eg: #361 & #466). It's easy enough to add this in and around the table without making it core functionality (see serverside-pagination example).

The library needs to leave out some things to keep it from becoming bloating and overcomplicated. When it comes to additional component rendering, I think it's best left to custom renders or author-provided functionality.

@gabrielliwerant it would be helpful in your serverside-pagination example if the loading indicator placement was not covered/hidden by the search box. Sure adding it outside the "paper" works, but does not feel right. I think a useful example of this as the example you reference attempts to be would be a good starting point for those wanting to elegantly add a loading indicator.

@anthonywebb Agreed, the examples provided are not the best. Would you have any interest in submitting something to enhance the example? I created an issue for this and linked it here.