[Discover 2.0][Feature Request] Persistent Column Width in Data Grid Table

[ananzh]

Is your feature request related to a problem? Please describe.

Our current implementation of the data grid table utilizes OuiDataGrid, which allows users to adjust the width of table columns. Users invest time customizing these settings to suit their preferences. To enhance user experience, it's beneficial to make these adjustments persistent across sessions.

Describe the solution you'd like

I propose three options to address this:

• Local Storage: Utilize the local storage capability provided by OpenSearch Dashboards' Storage service. This approach ensures that user preferences, such as specific column widths, are retained across browser sessions. However, this solution is not entirely permanent, as these settings can be lost if the user clears their browser storage. Additionally, this approach does not save the preferences in the saved search.

• State Storage: Store the column width settings in the application's state, possibly using Redux. When a user loads a table from a saved search, the application first checks for any saved column width settings in the state. This method provides a more integrated solution within the application's ecosystem.

• Hybrid Approach: Implement both local storage and state storage. This approach provides the benefits of both methods, ensuring a fallback mechanism if one fails and offering a more robust solution.

Additional Considerations

• It's important to balance user convenience with the potential risks of storing data in local storage, particularly concerning data privacy and security, which should not be a big deal given only column width.
• The implementation should be user-friendly, intuitive, and should seamlessly integrate with the existing user interface of OpenSearch Dashboards.
• A mechanism to revert to default settings might also be beneficial, providing users with an option to reset their customizations easily.