Create Core State

[theengineear]

[WIP: just wanted to push changes to plan.md up here]

Here's the types I ultimately want to end up with:

type CommunicationRecordProps = {
  contents: RecordOf<ContentsCommunicationRecordProps>,
  hosts: RecordOf<HostsCommunicationRecordProps>,
  kernels: RecordOf<KernelsCommunicationRecordProps>,
  kernelspecs: RecordOf<KernelspecsCommunicationRecordProps>,
  preferences: RecordOf<PreferencesCommunicationRecordProps>
};

type EntitiesRecordProps = {
  contents: RecordOf<ContentsEntitiesRecordProps>,
  hosts: RecordOf<HostsEntitiesRecordProps>,
  kernels: RecordOf<KernelsEntitiesRecordProps>,,
  kernelspecs: RecordOf<KernelspecsEntitiesRecordProps>,
  preferences: RecordOf<PreferencesRecordProps>
};

type CoreRecordProps = {
  selectedHostRef: ?HostRef,
  selectedContentRef: ?ContentRef,
  communication: RecordOf<CommunicationRecordProps>,
  entities: RecordOf<EntitiesRecordProps>
};

Then, I want to create a new reducer in /core that we export as core and that must be mounted at the top level of the state tree at core (maybe nteract as a namespace?) to work.

I want to get this state.core hunk mirroring the information that's currently in state.app, state.document, etc, etc and then start switching selectors over to the new sub-tree one-by-one.

This is mostly just documenting my own thoughts, but feel free to comment.

[theengineear]

@rgbkrk any objections?

[rgbkrk]

I assume you meant to stick the hostRef in the kernels byRef as well.

[rgbkrk]

👍

[lock]

Howdy! I'm 🔓🤖!

In order to keep information timely (based on the most recent release), we want all activity to be added to either new issues or open issues and PRs. In service to that goal, I, the lock bot close inactive closed issues when they haven't had activity in 120 days.

Feel free to open a new issue for related bugs and link to relevant comments from this thread.