Proposal: Use React context instead of prop drilling

[tortmayr]

What it does

• Refactor app component logic into a context provider
• Wrap the root component into the newly created MemoryAppProvider. This way child components can access the central state via context API and props drilling is no longer required.
• Refactor child components to access the central state info via context instead of props.

How to test

Full feature testing of the webview is required to ensure that everything works as before.

Review checklist

• [x] as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[tortmayr]

In general of course the use of context vs props is a compomise between encapsulation of components and duplication. However, as the React components of the memory view share large parts of state and props anyway, I lean towards using a React context here.

I agree. Regarding encapsulation: context sharing has to be explicitly enabled on a per-component basis. (Either by assigning the contextType property or the useContext hook). Currently only the options and the table widget use the shared context. Here as you already mentioned it makes sense because the share a very large part of the state anyways. If only a minor subset is required we can still fallback to props drilling to not expose the full state to the component. (e.g. How it is done for the MoreMemorySelect widget)