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

feat: simplify file upload #24

Merged
merged 6 commits into from
Jul 31, 2024
Merged

feat: simplify file upload #24

merged 6 commits into from
Jul 31, 2024

Conversation

joscha
Copy link
Member

@joscha joscha commented Jul 31, 2024

Summary by CodeRabbit

  • New Features

    • Enhanced file upload functionality to accept both File objects and file paths as strings.
    • Introduced a new helper function for streamlined file handling in uploads.
  • Bug Fixes

    • Improved type safety for file uploads with the implementation of a type guard function.
  • Tests

    • Added a new test case for uploading files from a specified path to improve testing coverage.
  • Chores

    • Updated package.json to specify a minimum required Node.js version of 20 or higher for better compatibility.

joscha added 6 commits July 30, 2024 12:02
Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/f4f322d1424aa547eba9cb092f905f5ceb9b639c' (2024-07-29)
  → 'github:NixOS/nixpkgs/3563397b2f10ffa1891e1a6ce99d13d960d73acd' (2024-07-30)
Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/3563397b2f10ffa1891e1a6ce99d13d960d73acd' (2024-07-30)
  → 'github:NixOS/nixpkgs/772f92db90637e4560a1d72f86099ccbce359cce' (2024-07-31)
Copy link

coderabbitai bot commented Jul 31, 2024

Walkthrough

This update enhances file upload functionality in the project by broadening the types of files that can be uploaded and streamlining the upload process. Additionally, it establishes clearer Node.js version requirements in configuration files. Overall, these changes improve compatibility and robustness in handling file uploads while refining project configurations.

Changes

File Change Summary
flake.nix Minor comment update for clarity regarding the publishing process.
package.json, scripts/build_npm.ts Added an engines field to specify that Node.js version 20 or higher is required for compatibility.
src/v1/entity_files.ts Modified UploadEntityFileRequest to accept SupportedFileType (File or string) and streamlined file handling in the EntityFiles class.
src/v1/tests/entity_files_test.ts Introduced a new test case for uploading files from a path, enhancing the test suite's coverage and functionality.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant EntityFiles
    participant FormData
    participant Blob

    User->>EntityFiles: Initiates file upload
    EntityFiles->>FormData: Append files
    alt File is a string
        FormData->>Blob: Convert string to Blob
    end
    FormData->>EntityFiles: Returns FormData
    EntityFiles->>User: Upload successful
Loading

🐇 In the garden, files take flight,
With paths and types, oh what a sight!
From strings to blobs, they weave and dance,
A joyful upload, a splendid chance!
So hop along, let data flow,
In our new world, watch progress grow! 🌼✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 449c7a2 and c516574.

Files ignored due to path filters (2)
  • flake.lock is excluded by !**/*.lock
  • src/v1/tests/__snapshots__/entity_files_test.ts.snap is excluded by !**/*.snap
Files selected for processing (5)
  • flake.nix (1 hunks)
  • package.json (1 hunks)
  • scripts/build_npm.ts (1 hunks)
  • src/v1/entity_files.ts (4 hunks)
  • src/v1/tests/entity_files_test.ts (2 hunks)
Files skipped from review due to trivial changes (1)
  • flake.nix
Additional comments not posted (9)
package.json (1)

18-20: LGTM! Node.js version requirement added.

The addition of the engines field specifying Node.js version >=20 ensures that the application runs in a compatible environment.

scripts/build_npm.ts (1)

57-59: LGTM! Node.js version requirement added to build configuration.

The addition of the engines field specifying Node.js version >=20 in the build configuration ensures that the built package declares the required Node.js version.

src/v1/tests/entity_files_test.ts (2)

14-16: LGTM! Imports added for path resolution.

The imports of path and fs modules and the definition of __dirname facilitate path resolution for the new test case.


74-98: LGTM! New test case for uploading files from path added.

The new test case for uploading files from a specified path improves the test coverage of the entityFiles module.

src/v1/entity_files.ts (5)

68-68: LGTM!

The new type SupportedFileType correctly broadens the file types that can be uploaded.


72-72: LGTM!

The updated type UploadEntityFileRequest correctly uses SupportedFileType[].


195-197: LGTM!

The upload function changes streamline the file handling process using appendToFormData.


226-228: LGTM!

The isFile function correctly acts as a type guard for File.


230-238: LGTM!

The appendToFormData function correctly handles both File and string types.

Comment on lines +240 to +253
// TODO(@joscha): replace with `import { openAsBlob } from "node:fs";` ASAP
function openAsBlob(filePath: string): Promise<Blob> {
return new Promise((resolve, reject) => {
const fileStream = fs.createReadStream(filePath)
const chunks: (string | ArrayBuffer)[] = []
fileStream.on('data', (chunk) => {
chunks.push(typeof chunk === 'string' ? chunk : chunk.buffer)
})
fileStream.on('end', () => {
resolve(new Blob(chunks))
})
fileStream.on('error', reject)
})
}
Copy link

Choose a reason for hiding this comment

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

LGTM! But replace with standard library function.

The openAsBlob function correctly converts file paths to Blob objects. However, there is a TODO comment indicating it should be replaced with a standard library function.

Do you want me to replace this function with the standard library function or open a GitHub issue to track this task?

@joscha joscha merged commit 3568bc8 into main Jul 31, 2024
8 checks passed
@joscha joscha deleted the joscha/simplify-file-upload branch July 31, 2024 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant