support prefix based deletion

[aayushshah15]

Important

Add prefix-based cache deletion support with updated documentation and tests.

• Behavior:
  • Add prefix input in src/main.ts for prefix-based cache deletion.
  • Allow key to be empty when prefix is true to delete all caches.
  • Modify deletion URL to append ?prefix when prefix is set.
• Documentation:
  • Update README.md to include prefix input in inputs table.
  • Add examples for prefix-based cache deletion and deleting all caches.
• Testing:
  • Add jest.config.js for test configuration.
  • Add tests in src/__tests__/main.test.ts for new prefix behavior and error handling.
• Dependencies:
  • Add jest, @types/jest, and ts-jest to package.json.

^{This description was created by for 51cfa0c. It will automatically update as commits are pushed.}

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 23f9500 in 33 seconds

More details

• Looked at 71 lines of code in 2 files
• Skipped 1 files when reviewing.
• Skipped posting 0 drafted comments based on config settings.

Workflow ID: wflow_lF0AvzLw14FAasde

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

⌛ 3 days left in your free trial, upgrade for $20/seat/month or contact us.

[ellipsis-dev]

👍 Looks good to me! Incremental review on c61f5e3 in 21 seconds

More details

• Looked at 71 lines of code in 2 files
• Skipped 1 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. src/main.ts:6

• Draft comment:
  When prefix is true, key can be empty, but getInput is set to required: true for key. Consider setting required: false and handling the empty case separately.
• Reason this comment was not posted:
  Comment was on unchanged code.

2. src/main.ts:19

• Draft comment:
  The URL modification for prefix-based deletion is correct and aligns with the PR description.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The code correctly appends ?prefix to the URL when prefix is true, which aligns with the PR description.

Workflow ID: wflow_6MQUMDhl2xwapTMe

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

⌛ 3 days left in your free trial, upgrade for $20/seat/month or contact us.

[ellipsis-dev]

❌ Changes requested. Incremental review on 706b7f0 in 56 seconds

More details

• Looked at 374 lines of code in 5 files
• Skipped 2 files when reviewing.
• Skipped posting 4 drafted comments based on config settings.

1. src/main.ts:23

• Draft comment:
  Ensure cacheToken is defined before making the fetch request to avoid unauthorized errors.
• Reason this comment was not posted:
  Comment did not seem useful.

2. src/main.ts:22

• Draft comment:
  Ensure repoName is defined before making the fetch request to avoid sending incorrect headers.
• Reason this comment was not posted:
  Comment did not seem useful.

3. src/main.ts:18

• Draft comment:
  Ensure baseUrl is defined before making the fetch request to avoid incorrect URL formation.
• Reason this comment was not posted:
  Comment did not seem useful.

4. src/main.ts:24

• Draft comment:
  Ensure region is defined before making the fetch request to avoid sending incorrect headers.
• Reason this comment was not posted:
  Comment did not seem useful.

Workflow ID: wflow_JWEqP9qGhpkPdDRW

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

⌛ 3 days left in your free trial, upgrade for $20/seat/month or contact us.

[ellipsis-dev]

The getInput call for key is marked as required, but the logic allows for an empty key when prefix is true. Consider removing the required: true option to align with the logic.

Suggested change

	const cacheKey = getInput("key", { required: true });
	const cacheKey = getInput("key");

[ellipsis-dev]

👍 Looks good to me! Incremental review on 5e51f74 in 19 seconds

More details

• Looked at 382 lines of code in 5 files
• Skipped 2 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. jest.config.js:14

• Draft comment:
  The Jest configuration looks good and follows best practices for TypeScript projects.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The jest.config.js file is correctly set up for TypeScript testing with Jest. The configuration is clear and follows best practices.

2. package.json:28

• Draft comment:
  The package.json is well-configured with necessary dependencies and scripts for building, formatting, linting, and testing.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The package.json file correctly includes the necessary dependencies and devDependencies for the project, including Jest and TypeScript support.

3. src/__tests__/main.test.ts:163

• Draft comment:
  The test cases are comprehensive and cover various scenarios for the deleteCache function, including success, 404, and error cases.
• Reason this comment was not posted:
  Confidence changes required: 0%
  The test file is well-structured and covers various scenarios for the deleteCache function, including success, 404, and error cases.

Workflow ID: wflow_zvyp5vfBqBzkYpf8

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

⌛ 3 days left in your free trial, upgrade for $20/seat/month or contact us.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 51cfa0c in 21 seconds

More details

• Looked at 383 lines of code in 5 files
• Skipped 2 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. src/__tests__/main.test.ts:13

• Draft comment:
  Ensure that jest.mocked(fetch) is correctly typed for better type safety. This is important for maintaining type integrity in tests.
• Reason this comment was not posted:
  Confidence changes required: 20%
  The test file is correctly structured, but the mock for node-fetch should ensure that the fetch function is properly typed. The current usage of jest.mocked(fetch) is correct, but it's good to ensure that the mock is typed correctly for better type safety.

2. src/main.ts:23

• Draft comment:
  Consider adding a check to ensure cacheToken is not undefined before making the fetch request to prevent potential runtime errors.
• Reason this comment was not posted:
  Confidence changes required: 30%
  The deleteCache function in main.ts is well-structured, but it could benefit from additional validation for the cacheToken to ensure it's not undefined before making the fetch request. This would prevent potential runtime errors.

Workflow ID: wflow_Ro6akheyjmBQndFy

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

⌛ 3 days left in your free trial, upgrade for $20/seat/month or contact us.