-
Notifications
You must be signed in to change notification settings - Fork 531
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
Revert "Revert "Enable noUncheckedIndexedAccess for loader packages (#21485)"" #23064
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Coverage Summary
↓ packages.loader.container-loader.src:
Line Coverage Change: -0.01% Branch Coverage Change: No change
Metric Name | Baseline coverage | PR coverage | Coverage Diff |
---|---|---|---|
Branch Coverage | 91.28% | 91.28% | → No change |
Line Coverage | 94.61% | 94.60% | ↓ -0.01% |
↑ packages.loader.driver-utils.src:
Line Coverage Change: 0.01% Branch Coverage Change: No change
Metric Name | Baseline coverage | PR coverage | Coverage Diff |
---|---|---|---|
Branch Coverage | 90.06% | 90.06% | → No change |
Line Coverage | 81.93% | 81.94% | ↑ 0.01% |
↑ packages.loader.driver-utils.src.adapters.compression.summaryblob:
Line Coverage Change: 0.02% Branch Coverage Change: No change
Metric Name | Baseline coverage | PR coverage | Coverage Diff |
---|---|---|---|
Branch Coverage | 84.37% | 84.37% | → No change |
Line Coverage | 96.15% | 96.17% | ↑ 0.02% |
↑ packages.loader.driver-utils.src.protocol:
Line Coverage Change: 0.26% Branch Coverage Change: No change
Metric Name | Baseline coverage | PR coverage | Coverage Diff |
---|---|---|---|
Branch Coverage | 73.33% | 73.33% | → No change |
Line Coverage | 86.53% | 86.79% | ↑ 0.26% |
Baseline commit: c7730cc
Baseline build: 306006
Happy Coding!!
Code coverage comparison check passed!!
⯅ @fluid-example/bundle-size-tests: +292 Bytes
Baseline commit: c7730cc |
Copilot
AI
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 5 out of 13 changed files in this pull request and generated 1 suggestion.
Files not reviewed (8)
- packages/loader/container-loader/tsconfig.json: Language not supported
- packages/loader/driver-utils/tsconfig.json: Language not supported
- packages/loader/driver-utils/src/prefetchDocumentStorageService.ts: Evaluated as low risk
- packages/loader/driver-utils/src/insecureUrlResolver.ts: Evaluated as low risk
- packages/loader/driver-utils/src/parallelRequests.ts: Evaluated as low risk
- packages/loader/container-loader/src/connectionManager.ts: Evaluated as low risk
- packages/loader/container-loader/src/containerStorageAdapter.ts: Evaluated as low risk
- packages/loader/driver-utils/src/protocol/gitHelper.ts: Evaluated as low risk
Comments skipped due to low confidence (5)
packages/loader/container-loader/src/serializedStateManager.ts:416
- Ensure that
attributesHash
andsnapshotBlobs[attributesHash]
are non-null before using non-null assertions. The TODO comment suggests further investigation is needed.
const attributes = JSON.parse(snapshotBlobs[attributesHash!]!);
packages/loader/container-loader/src/utils.ts:155
- The non-null assertion on 'summary.tree[key]' should be reviewed to ensure it cannot be null or undefined.
// eslint-disable-next-line @typescript-eslint/no-non-null-assertion
packages/loader/container-loader/src/utils.ts:431
- The non-null assertion on 'attributesHash' should be reviewed to ensure it cannot be null or undefined.
// eslint-disable-next-line @typescript-eslint/no-non-null-assertion
packages/loader/driver-utils/src/adapters/compression/summaryblob/documentStorageServiceSummaryBlobCompressionAdapter.ts:66
- Accessing the first element of the buffer without checking if the buffer is empty could lead to an error. Consider adding a check to ensure
blob
is not empty before accessing its first element.
const firstByte = IsoBuffer.from(blob)[0]!;
packages/loader/driver-utils/src/adapters/compression/summaryblob/documentStorageServiceSummaryBlobCompressionAdapter.ts:96
- Accessing the first element of the buffer without checking if the buffer is empty could lead to an error. Consider adding a check to ensure
blob
is not empty before accessing its first element.
const firstByte = IsoBuffer.from(blob)[0]!;
Tip: If you use Visual Studio Code, you can request a review from Copilot before you push from the "Source Control" tab. Learn more
IsoBuffer.from(blob)[0] & 0x0f; | ||
: // TODO why are we non null asserting here? | ||
// eslint-disable-next-line no-bitwise, @typescript-eslint/no-non-null-assertion | ||
IsoBuffer.from(blob)[0]! & 0x0f; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Accessing the first element of the buffer without checking if the buffer is empty could lead to an error. Consider adding a check to ensure blob
is not empty before accessing its first element.
Copilot is powered by AI, so mistakes are possible. Review output carefully before use.
Reverts #22380