Add package uploading feature

[Oksamies]

No description provided.

[Oksamies]

• Add package uploading feature #1435 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

To fix the problem, we need to remove the unused chainActions function from the code. This will eliminate the ESLint error and clean up the code by removing unnecessary definitions.

• Locate the chainActions function definition in the file packages/ts-uploader/src/tasks/chain.ts.
• Remove the entire function definition, including its type definition and implementation.

To fix the problem, we need to replace the any type with a more specific type that accurately represents the possible values for abortReason. Since abortReason is used in the context of an AbortController, it should be of type DOMException or undefined, as these are the types typically associated with abort reasons in the DOM API.

To fix the problem, we need to replace the any type with a more specific type that accurately represents the possible values for the reason parameter. In this case, the reason parameter for the abort method of AbortController can be of any type, but it is often a string, an error, or undefined. We can use a union type to represent this.

We will replace the any type with a union type that includes string, Error, and undefined. This will provide better type safety while still allowing for the flexibility needed for the reason parameter.

To fix the problem, we need to remove the unused variable _error from the code. This will eliminate the ESLint warning and make the code cleaner and easier to maintain. The best way to fix this is to update the retryPolling function to remove the _error parameter from the then method's second callback function.

To fix the problem, we need to remove the unused variable _error from the code. This will resolve the ESLint warning and clean up the code. The best way to fix this without changing existing functionality is to remove the _error parameter from the function definition on line 306.

To fix the problem, we need to remove the unused variable _key from the forEach callback function. This can be done by using a different parameter signature that only includes the used variable value. This change should be applied to all instances where _key is defined but not used.

To fix the problem, we need to remove the unused _key variable from the forEach loop in the pause, resume, and retry methods. This will eliminate the ESLint warning and improve the code quality. Specifically, we will update the forEach loop to only include the value parameter, which is actually used in the loop body.

The best way to fix the problem is to remove the unused variable _key from the forEach loop. This will resolve the ESLint error without changing the existing functionality of the code. The variable _key is not used within the loop, so its removal will not affect the logic of the code.

To implement this fix, we need to edit the forEach loops in the pause, resume, and retry methods to remove the _key variable. This involves changing the parameter list of the forEach callback function to only include the value parameter.