Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improvement(client): misc cleanup #23959

Merged
merged 3 commits into from
Mar 11, 2025

Conversation

jason-ha
Copy link
Contributor

  • Cleanup IContainerRuntimeOptionsInternal use versus IContainerRuntimeOptions
    (prep for future expansion)
  • Comment corrections, enhancement, and cleanup
  • Type-only imports for containerRuntime.ts externals

- Cleanup `IContainerRuntimeOptionsInternal` use versus `IContainerRuntimeOptions`
  (prep for future expansion)
- Comment corrections, enhancement, and cleanup
- Type-only imports for containerRuntime.ts externals
@jason-ha jason-ha requested review from Copilot and markfields and removed request for Copilot February 28, 2025 22:59
@github-actions github-actions bot added area: runtime Runtime related issues base: main PRs targeted against main branch labels Feb 28, 2025
@@ -952,7 +957,7 @@ export class ContainerRuntime
context: IContainerContext;
registryEntries: NamedFluidDataStoreRegistryEntries;
existing: boolean;
runtimeOptions?: IContainerRuntimeOptions; // May also include options from IContainerRuntimeOptionsInternal
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any changes here should also happen for loadContainerRuntime free function (see LoadContainerRuntimeParams). We probably should update this to use that params type. Or just get rid of it, unless we really need an internal version that returns concrete ContainerRuntime

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, obviously we can't make these changes on LoadContainerRuntimeParams because that's not @internal. This is fine for now.

@@ -1552,7 +1557,7 @@ export class ContainerRuntime
electedSummarizerData: ISerializedElection | undefined,
chunks: [string, string[]][],
dataStoreAliasMap: [string, string][],
baseRuntimeOptions: Readonly<Required<IContainerRuntimeOptions>>,
runtimeOptions: Readonly<Required<IContainerRuntimeOptionsInternal>>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yay

Comment on lines 1886 to 1887
// Can the `content` argument type be IEnvelope?
// verifyNotClosed is called in FluidDataStoreContext, which is *the* expected caller.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a note to self? Not sure it should be checked in in its current state

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not self notes really. I changed the first to be a Future: comment and the latter is just interesting to know.
I do have work in progress for the new addressing pattern. That made me think about the call flow; so, I captured the verifyNoClosed note.

@jason-ha jason-ha requested a review from markfields March 10, 2025 23:59
@jason-ha jason-ha enabled auto-merge (squash) March 11, 2025 00:00
@jason-ha jason-ha merged commit b95855e into microsoft:main Mar 11, 2025
35 checks passed
chentong7 pushed a commit to chentong7/FluidFramework that referenced this pull request Mar 11, 2025
- Cleanup `IContainerRuntimeOptionsInternal` use versus
`IContainerRuntimeOptions`
  (prep for future expansion)
- Comment corrections, enhancement, and cleanup
- Type-only imports for containerRuntime.ts externals
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: runtime Runtime related issues base: main PRs targeted against main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants