feat: use prettier, oxlint and vitest #27

fengmk2 · 2025-05-10T04:53:41Z

Summary by CodeRabbit

New Features
- Introduced a pre-commit hook to enforce code quality on staged files.
- Added configuration files for OXLint and Prettier to standardize linting and formatting.
- Updated lint-staged to automatically fix code style on commit.
Chores
- Migrated project tooling from ESLint and egg-bin to OXLint, Prettier, and Vitest.
- Updated CI workflows to use newer Node.js and Codecov versions.
- Removed ESLint configuration and dependencies.
- Improved environment variable handling in test configuration.
Documentation
- Enhanced README formatting for clarity and readability.
Refactor & Style
- Improved code formatting, type annotations, and consistency across all modules.
- Refined method and function signatures for better type safety and readability.
- Updated test files to use Vitest conventions and improved assertion clarity.
Tests
- Migrated tests to Vitest and updated test hooks and assertions for consistency.

coderabbitai · 2025-05-10T04:53:48Z

Walkthrough

This update migrates the project's linting, formatting, and testing toolchain from ESLint, Egg-Bin, and Mocha to OXLint, Prettier, and Vitest. It removes the ESLint configuration, introduces OXLint and Prettier configs, updates scripts and dependencies, and refactors code and tests for improved style, type safety, and compatibility with the new tools.

Changes

File(s)	Change Summary
.eslintrc	Removed ESLint configuration file, discontinuing ESLint rules and TypeScript/node prefix enforcement.
.oxlintrc.json	Added OXLint configuration with strict rules, multiple plugins, and ignore patterns tailored for Node.js, TypeScript, and Mocha environments.
.prettierrc, .prettierignore	Introduced Prettier configuration and ignore file to standardize formatting and exclude changelog and snapshots from formatting.
.husky/pre-commit	Added pre-commit hook to run lint-staged for linting and formatting staged files before commits.
.github/workflows/nodejs.yml	Updated CI workflow: replaced Node.js v23 with v24, upgraded Codecov action to v5, and adjusted indentation.
.github/workflows/release.yml	Reformatted branch specification in workflow trigger for consistency (no logic change).
package.json	Migrated scripts to use OXLint, Prettier, and Vitest; replaced lint, test, and coverage tools; added lint-staged and husky; updated devDependencies accordingly.
README.md	Improved documentation formatting: standardized code blocks, added markdown tables, and clarified code examples. No API or behavior changes.
src/OSSBaseClient.ts, src/OSSObject.ts, src/type/Object.ts, src/type/Request.ts	Refactored for improved formatting, multiline signatures, explicit type imports, and minor type safety enhancements; replaced assert() with assert.ok(); improved XML and error handling robustness; no logic changes.
src/util/checkBucketName.ts, src/util/checkObjectTag.ts, src/util/encodeCallback.ts,	Reformatted conditionals and error messages for clarity; improved type safety and explicitness in validation and encoding utilities.
src/util/json2xml.ts	Changed function parameter type from `any` to `unknown` for stricter type safety; reformatted for readability.
src/util/policyToJSONString.ts	Improved error handling in JSON parsing with type-safe error message extraction.
src/util/sign.ts	Reformatted function signatures and loops for clarity; no change in signature logic or control flow.
src/error/OSSClientError.ts	Reformatted constructor to multiline style for readability; no logic changes.
test/OSSObject.test.ts	Refactored tests: used assert.ok, updated to Vitest hooks, replaced urllib import, improved assertion formatting, and enhanced type assertions. No test logic changes.
test/config.ts	Used `read-env-value` for robust environment variable handling with defaults; replaced process.env access.
test/util/isIP.test.ts	Imported Vitest's `describe` and `it` for BDD-style test definitions; no logic changes.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant Git as Git (with Husky)
    participant Lint as OXLint/Prettier
    participant Test as Vitest
    participant CI as GitHub Actions

    Dev->>Git: git commit
    Git->>Lint: Run lint-staged (OXLint, Prettier) on staged files
    Lint-->>Git: Lint passes or fails
    Git->>Dev: Commit proceeds or aborts

    Dev->>CI: Push to repository
    CI->>Lint: Run OXLint on codebase
    CI->>Test: Run Vitest with coverage
    Test->>CI: Test results and coverage
    CI->>Dev: CI status (pass/fail)

Possibly related PRs

test: Node.js 23 #23: Related update to Node.js CI workflow matrix adding Node.js v23, while this PR replaces v23 with v24, both modifying the same workflow file.

Poem

🐇✨ In the warren, tools renewed,
Prettier and OXLint now pursued.
Vitest hops where Mocha lay,
Husky guards each commit’s way.
Scripts refactored, code refined,
A burrow clean and well-aligned.
🐰🎉 Hooray for lint and test anew!

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bb6d832 and f2a92e5.

📒 Files selected for processing (2)

package.json (2 hunks)
test/OSSObject.test.ts (81 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

test/OSSObject.test.ts
package.json

⏰ Context from checks skipped due to timeout of 90000ms (4)

GitHub Check: build (18, ubuntu-latest)
GitHub Check: build (22, ubuntu-latest)
GitHub Check: build (20, ubuntu-latest)
GitHub Check: build (24, ubuntu-latest)

✨ Finishing Touches

📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

Copilot

Pull Request Overview

This PR introduces a new code style and quality workflow by integrating prettier, oxlint, and vitest while refactoring several modules for improved readability and maintainability. Key changes include reformatting functions into multi‐line signatures, standardizing assertions (using assert.ok), updating configuration files, and adjusting type declarations and error handling.

Reviewed Changes

Copilot reviewed 23 out of 23 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/util/sign.ts	Refactored function signatures and loop iterations for clarity.
src/util/policyToJSONString.ts	Improved error message handling for JSON parsing.
src/util/json2xml.ts	Updated type annotations and recursive call formatting.
src/util/encodeCallback.ts	Adjusted formatting for base64 conversion, improving readability.
src/util/checkObjectTag.ts	Simplified condition structure and error messages.
src/util/checkBucketName.ts	Reformatted regex condition for bucket name validation.
src/type/*	Updated union types’ formatting and multiline declarations.
src/OSSObject.ts	Converted assertions to assert.ok, clarified overloads & mappings.
src/OSSBaseClient.ts	Improved assertion messaging and updated internal request logic.
package.json & config files	Updated dependencies & scripts to use prettier, oxlint, vitest, husky.
.github/workflows/nodejs.yml	Updated Node versions and Codecov action version.
README.md	Adjusted API usage examples to improved formatting.

socket-security · 2025-05-10T04:54:13Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	husky@9.1.7
	@vitest/coverage-v8@3.1.3
	read-env-value@1.0.1
	vitest@3.1.3
	oxlint@0.16.10
	prettier@3.5.3

View full report

coderabbitai

Actionable comments posted: 2

🔭 Outside diff range comments (4)

.husky/pre-commit (1)
1-2: ⚠️ Potential issue

Missing Husky hook initialization
Husky requires sourcing its runner script before commands. Without it, the hook may not run.

Apply this diff:
+#!/usr/bin/env sh
+. "$(dirname "$0")/_/husky.sh"
 npx lint-staged
test/OSSObject.test.ts (1)
1486-1486: ⚠️ Potential issue

Fix timeout in traffic limit test.

The test "should signature url with traffic limit" is timing out in 5000ms, which is causing build failures:
Test timed out in 5000ms for 'should signature url with traffic limit'. Consider increasing timeout with 'testTimeout' option.
Increase the test timeout specifically for this test:
-  it('should signature url with traffic limit', async () => {
+  it('should signature url with traffic limit', async () => {
+    // This test involves network operations that may take longer than the default timeout
+    vi.setConfig({ testTimeout: 30000 });
Or use the testTimeout option in the test declaration:
-  it('should signature url with traffic limit', async () => {
+  it('should signature url with traffic limit', { timeout: 30000 }, async () => {
🧰 Tools

🪛 GitHub Check: build (24, ubuntu-latest)

[failure] 1486-1486: test/OSSObject.test.ts > test/OSSObject.test.ts > signatureUrl() and asyncSignatureUrl() > should signature url with traffic limit
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/OSSObject.test.ts:1486:5

🪛 GitHub Check: build (20, ubuntu-latest)

[failure] 1486-1486: test/OSSObject.test.ts > test/OSSObject.test.ts > signatureUrl() and asyncSignatureUrl() > should signature url with traffic limit
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/OSSObject.test.ts:1486:5

🪛 GitHub Check: build (18, ubuntu-latest)

[failure] 1486-1486: test/OSSObject.test.ts > test/OSSObject.test.ts > signatureUrl() and asyncSignatureUrl() > should signature url with traffic limit
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/OSSObject.test.ts:1486:5

🪛 GitHub Check: build (22, ubuntu-latest)

[failure] 1486-1486: test/OSSObject.test.ts > test/OSSObject.test.ts > signatureUrl() and asyncSignatureUrl() > should signature url with traffic limit
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/OSSObject.test.ts:1486:5

🪛 GitHub Actions: Node.js CI

[error] 1486-1486: Test timed out in 5000ms for 'should signature url with traffic limit'. Consider increasing timeout with 'testTimeout' option.
src/util/sign.ts (1)
32-40: ⚠️ Potential issue

Canonicalization sort only compares first character – breaks signature for multi-char keys

compareFunc returns a result based solely on entry[0], so keys like "abc" and "az" are treated as equal.
When OSS validates the signature it expects keys to be sorted by the full string; a wrong order yields SignatureDoesNotMatch.
-const compareFunc = (entry1: string, entry2: string) => {
-  if (entry1[0] > entry2[0]) {
-    return 1;
-  } else if (entry1[0] < entry2[0]) {
-    return -1;
-  }
-  return 0;
-};
+const compareFunc = (a: string, b: string) => (a > b ? 1 : a < b ? -1 : 0);
This keeps the original intent but performs a full lexical comparison.

Also applies to: 47-49
src/OSSObject.ts (1)
384-388: ⚠️ Potential issue

Destroying the write stream immediately causes “ERR_STREAM_UNABLE_TO_PIPE”

CI shows failures (Cannot pipe to a closed or destroyed stream) in tests that pass a file path to get().
urllib resolves the promise when the response ends, not when the writeStream finishes flushing.
Calling writeStream.destroy() at this point closes the FD early and triggers the error.
-      if (needDestroy && writeStream) {
-        writeStream.destroy();
-      }
+      // Wait for the stream to flush before closing it
+      if (needDestroy && writeStream) {
+        await new Promise<void>(resolve => {
+          writeStream.once('close', resolve);
+        });
+      }
This lets the OS flush and close the descriptor safely, removing the pipeline failure.

🧹 Nitpick comments (10)

test/util/isIP.test.ts (1)

3-3: Optional: Adopt Vitest's expect API.
Consider importing and using Vitest's expect for assertions (expect(isIP(...)).toBe(true)) to leverage built-in matchers and improve readability.
src/util/checkBucketName.ts (1)
5-6: Nitpick: Improve error message grammar.
Change the error message from:
'The bucket must be conform to the specifications'
to:
'The bucket must conform to the specifications'
src/util/encodeCallback.ts (1)
20-22: Optional: Extract base64 encoding to helper.
Consider defining a helper such as:
function toBase64(obj: unknown): string {
  return Buffer.from(JSON.stringify(obj)).toString('base64');
}
to reduce duplication and centralize encoding logic.

Also applies to: 32-34
src/util/checkObjectTag.ts (2)
8-10: Grammar refinement in error message
The message reads “maximum of 10 tags for a object” but should use “an object.”

Proposed diff:
-    throw new TypeError('maximum of 10 tags for a object');
+    throw new TypeError('maximum of 10 tags for an object');
12-14: Grammar refinement in error message
Use plural “strings” and lowercase for consistency.

Proposed diff:
-      throw new TypeError('the key and value of the tag must be String');
+      throw new TypeError('the key and value of the tag must be strings');
src/util/json2xml.ts (1)
4-5: Optional refactor: extract options interface
If you expect more flags later, consider:
interface Json2XmlOptions { headers?: boolean }
export function json2xml(
  json: Record<string, unknown>,
  options?: Json2XmlOptions
)
README.md (1)
1-1658: Approve documentation formatting changes
Prettier has reformatted code snippets, lists, and tables without altering any API descriptions or examples.

Grammar nitpick in .deleteMulti description
Fix typo “succes” → “success”, add missing comma/semicolon.
- quiet mode: if all objects delete succes, return emtpy response. otherwise return delete error object results.
+ quiet mode: if all objects delete successfully, return empty response; otherwise, return delete error object results.
🧰 Tools

🪛 LanguageTool

[uncategorized] ~26-~26: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... OSS, Object Storage Service. Equal to well known Amazon S3....

(EN_COMPOUND_ADJECTIVE_INTERNAL)

[grammar] ~146-~146: An article may be missing.
Context: ... aliyun too, you can set true to save lot of money. - [timeout] {String|Number} inst...

(BUNCH_OF)

[grammar] ~166-~166: There seems to be a noun/verb agreement error. Did you mean “accelerates” or “accelerated”?
Context: ...ion: 'oss-cn-hangzhou', }); ``` 2. use accelerate endpoint - Global accelerate endpoint:...

(SINGULAR_NOUN_VERB_AGREEMENT)

[uncategorized] ~405-~405: Possible missing article found.
Context: ...nd an object to the bucket, it's almost same as put, but it can add content to exist...

(AI_HYDRA_LEO_MISSING_THE)

[uncategorized] ~405-~405: Possible missing article found.
Context: ... same as put, but it can add content to existing object rather than override it. All pa...

(AI_HYDRA_LEO_MISSING_AN)

[uncategorized] ~448-~448: Possible missing preposition found.
Context: ...e baseUrl, will use baseUrl instead the default bucket and endpoint. Suggest ...

(AI_HYDRA_LEO_MISSING_OF)

[grammar] ~550-~550: Possible subject-verb agreement error.
Context: ... example: - Head an exists object and get object meta info ```js await this.stor...

(IS_AND_ARE)

[grammar] ~718-~718: In standard English, the word ‘exists’ is a verb. Please verify that the determiner ‘an’ is correct, or that a noun is not missing between ‘an’ and ‘exists’.
Context: ...lso delete success. example: - Delete an exists object ```js await store.delete('ossde...

(A_INFINITIVE)

[grammar] ~745-~745: It seems that a pronoun is missing.
Context: ... [sourceBucket] {String} source Bucket. if doesn't exist，sourceBucket is same bu...

(IF_VB)

[grammar] ~745-~745: Is an article like ‘a’ or ‘an’ missing?
Context: ...Bucket. if doesn't exist，sourceBucket is same bucket. - [options] {Object} optio...

(BE_NN)

[uncategorized] ~745-~745: Possible missing article found.
Context: ...ket. if doesn't exist，sourceBucket is same bucket. - [options] {Object} optional p...

(AI_HYDRA_LEO_MISSING_THE)

[grammar] ~809-~809: In standard English, the word ‘exists’ is a verb. Please verify that the determiner ‘an’ is correct, or that a noun is not missing between ‘an’ and ‘exists’.
Context: ...## .putMeta(name, meta[, options]) Set an exists object meta. parameters: - name {Stri...

(A_INFINITIVE)

[uncategorized] ~857-~857: The preposition ‘at’ seems more likely in this position.
Context: ...Object>} object names, max 1000 objects in once. - key {String} object name - ...

(AI_HYDRA_LEO_REPLACE_IN_AT)

[uncategorized] ~863-~863: Possible missing comma found.
Context: ...lete succes, return emtpy response. otherwise return delete error object results. ...

(AI_HYDRA_LEO_MISSING_COMMA)

[grammar] ~928-~928: The modal verb ‘will’ requires the verb’s base form.
Context: ...meta info list Each ObjectMeta will contains blow properties: - name {String} obje...

(MD_BASEFORM)

[uncategorized] ~947-~947: Possible missing preposition found.
Context: ...t total use time (ms) example: - List top 10 objects ```js const result = await ...

(AI_HYDRA_LEO_MISSING_OF)

[grammar] ~993-~993: The modal verb ‘will’ requires the verb’s base form.
Context: ...meta info list Each ObjectMeta will contains blow properties: - name {String} obje...

(MD_BASEFORM)

[uncategorized] ~1013-~1013: Possible missing preposition found.
Context: ...er} request total use time (ms) - List top 10 objects ```js const result = await ...

(AI_HYDRA_LEO_MISSING_OF)

[grammar] ~1072-~1072: The modal verb ‘will’ requires the verb’s base form.
Context: ...meta info list Each ObjectMeta will contains blow properties: - name {String} obje...

(MD_BASEFORM)

[grammar] ~1128-~1128: There is an agreement error between ‘put’ and ‘object’. Insert ‘a(n)’ or change the noun to plural.
Context: ...for download or upload object. When you put object with signatureUrl ,you need to pass `Co...

(PRP_VB_NN)

[uncategorized] ~1151-~1151: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...ject} set the custom value for callback,eg. {var1: value1,var2:value2} Success wil...

(E_G)

[typographical] ~1208-~1208: Consider adding a comma after ‘Basically’ for more clarity.
Context: ...## .asyncSignatureUrl(name[, options]) Basically the same as signatureUrl, if refreshSTS...

(RB_LY_COMMA)

[uncategorized] ~1232-~1232: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...ject} set the custom value for callback,eg. {var1: value1,var2:value2} Success wil...

(E_G)

[misspelling] ~1312-~1312: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ssdemo.txt', 'public-read'); - Set an history object's ACL js const versi...

(EN_A_VS_AN)

[misspelling] ~1350-~1350: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...'); console.log(result.acl); - Get an history object's ACL js const versi...

(EN_A_VS_AN)

[misspelling] ~1404-~1404: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...sole.log(result.status); - Restore an history object js const versionId =...

(EN_A_VS_AN)

[uncategorized] ~1534-~1534: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...ng} the object name - tag {Object} tag, eg. {var1: value1,var2:value2} - [options...

(E_G)

[uncategorized] ~1552-~1552: The abbreviation “e.g.” (= for example) requires two periods.
Context: ...ng} the object name - tag {Object} tag, eg. {var1: value1,var2:value2} - [options...

(E_G)

[grammar] ~1592-~1592: The modal verb ‘will’ requires the verb’s base form.
Context: ...s Each error return by OSS server will contains these properties: - name {String} erro...

(MD_BASEFORM)

🪛 markdownlint-cli2 (0.17.2)

184-184: Bare URL used
null

(MD034, no-bare-urls)
test/OSSObject.test.ts (1)
702-714: Use consistent Buffer utility methods.

The implementation uses both Buffer.byteLength and string concatenation to determine content length.

For better readability, consider:
-  'content-length': Buffer.byteLength(
-    'Hello, 你好 OSS',
-    'utf8'
-  ).toString(),
+  'content-length': String(Buffer.byteLength('Hello, 你好 OSS', 'utf8')),
src/OSSObject.ts (1)
1096-1098: successStatuses too narrow for PUT/POST uploads

OSS may legitimately return 201 (Created) for some PUT/POST operations (e.g. object upload with x-oss-forbid-overwrite). Limiting to [200] forces an unnecessary retry path.
-    params.successStatuses = [200];
+    params.successStatuses = [200, 201];
src/OSSBaseClient.ts (1)
190-194: Avoid double allocation when computing MD5

Buffer.from(params.content) allocates a new buffer although params.content is already a Buffer.
-        headers['content-md5'] = createHash('md5')
-          .update(Buffer.from(params.content))
+        headers['content-md5'] = createHash('md5')
+          .update(params.content)
           .digest('base64');
Reduces one copy per request and a few CPU cycles.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1f7c506 and bb6d832.

📒 Files selected for processing (23)

.eslintrc (0 hunks)
.github/workflows/nodejs.yml (1 hunks)
.github/workflows/release.yml (1 hunks)
.husky/pre-commit (1 hunks)
.oxlintrc.json (1 hunks)
.prettierignore (1 hunks)
.prettierrc (1 hunks)
README.md (42 hunks)
package.json (2 hunks)
src/OSSBaseClient.ts (11 hunks)
src/OSSObject.ts (47 hunks)
src/error/OSSClientError.ts (1 hunks)
src/type/Object.ts (2 hunks)
src/type/Request.ts (1 hunks)
src/util/checkBucketName.ts (1 hunks)
src/util/checkObjectTag.ts (1 hunks)
src/util/encodeCallback.ts (2 hunks)
src/util/json2xml.ts (2 hunks)
src/util/policyToJSONString.ts (1 hunks)
src/util/sign.ts (5 hunks)
test/OSSObject.test.ts (81 hunks)
test/config.ts (1 hunks)
test/util/isIP.test.ts (1 hunks)

💤 Files with no reviewable changes (1)

.eslintrc

🧰 Additional context used

🧬 Code Graph Analysis (2)

src/util/sign.ts (3)

src/type/Request.ts (2)

RequestParameters (5-8)

Request (18-21)

src/OSSObject.ts (2)

method (1140-1155)

options (1118-1135)

src/OSSBaseClient.ts (4)

request (234-263)

signature (71-74)

authorization (91-109)

options (267-292)

src/OSSBaseClient.ts (3)

src/type/Request.ts (3)

RequestParameters (5-8)

OSSRequestParams (23-44)

OSSResult (46-49)

src/util/sign.ts (2)

buildCanonicalString (65-94)

authorization (104-111)

src/error/OSSClientError.ts (1)

OSSClientError (5-28)

🪛 LanguageTool

README.md

[uncategorized] ~863-~863: Possible missing comma found.
Context: ...lete succes, return emtpy response. otherwise return delete error object results. ...

(AI_HYDRA_LEO_MISSING_COMMA)

🪛 Biome (1.9.4)

.oxlintrc.json

[error] 26-26: Expected a property but instead found '// eslint'.

Expected a property here.

(parse)

[error] 27-27: End of file expected