[Table]: should we support lazy loading of the children rows. If so we'll need some UX to indicate this expansion is loading

[matsgothe]

This design should state the behavior of the table when a parent node is expanded

• [default] Expanding a row will lazy load the child rows
• [default] The selection of (non-loaded) child rows will depend on the selection of the parent row. Unselected parent will load unselected child rows. A selected parent will load selected child rows.
• A progress indicator should show the lazy loading of child rows. The implementation may set a time threshold when to start showing a progress indicator. E.g. if loading passes 3 seconds limit.
• The progress indicator should be visually located close to the user action location, i.e. the chevron. For example to the left side of the table row.
• The progress indicator should be consistent with other loading / progress indicator. E.g. a swiping bar.

This design should be visually consistent with the action progress indicator in issue https://github.com/IBM/carbon-addons-iot-react/issues/128

[davidicus]

This issue is stale. Closing. Please re-open if needed.

[matsgothe]

This is a required table feature. With production systems in Monitor we will have 100.000 IO points in a hierarchical tree. That can not be loaded into the table. Lazy loading is required. My take is that there is no simple/intuitive way to do paging in a hierarchical tree. The 'paging' feature is the lazy loading. Hence this is a must for enterprise scale use. @amymillett