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

fix: update canvas size to avoid white space on result #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

paodb
Copy link
Member

@paodb paodb commented Dec 18, 2024

Close #7

Summary by CodeRabbit

  • New Features
    • Enhanced image cropping functionality with improved canvas dimension calculations.
    • Introduced support for circular cropping options.

Copy link

coderabbitai bot commented Dec 18, 2024

Walkthrough

The pull request modifies the image-crop.tsx file, specifically the croppedImageEncode method in the ImageCropElement class. The changes focus on refining the canvas dimension calculation during image cropping. The implementation now calculates canvas width and height by multiplying crop dimensions with the pixel ratio, simplifying the previous approach that considered both crop dimensions and image's natural dimensions.

Changes

File Change Summary
src/main/resources/META-INF/resources/frontend/src/image-crop.tsx Modified croppedImageEncode method to simplify canvas dimension calculation

Assessment against linked issues

Objective Addressed Explanation
Resolve extra white space in cropped image [#7]
Ensure tight cropping without adjacent white space

The changes directly address the reported issue of extra white space in the cropped image by modifying the canvas dimension calculation. The implementation now appears to create a more precise crop that should eliminate unnecessary white space around the selected image area.


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>, 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.

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. (Beta)
  • @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.

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 UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 860226f and dc86abd.

📒 Files selected for processing (1)
  • src/main/resources/META-INF/resources/frontend/src/image-crop.tsx (1 hunks)
🔇 Additional comments (1)
src/main/resources/META-INF/resources/frontend/src/image-crop.tsx (1)

92-93: LGTM! Canvas dimension calculation looks correct.

The new implementation properly handles high-DPI displays by scaling the canvas dimensions with the device pixel ratio, which should fix the white space issue.

Comment on lines +92 to +93
canvas.width = ccrop.width * pixelRatio;
canvas.height = ccrop.height * pixelRatio;
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider unifying the canvas dimension handling for both crop types.

The circular crop case immediately overrides the canvas dimensions without considering the pixel ratio, which could lead to inconsistent quality between regular and circular crops on high-DPI displays.

Consider applying this change:

-    canvas.width = ccrop.width * pixelRatio;
-    canvas.height = ccrop.height * pixelRatio;
+    const finalWidth = circularCrop ? ccrop.width : ccrop.width * pixelRatio;
+    const finalHeight = circularCrop ? ccrop.height : ccrop.height * pixelRatio;
+    canvas.width = finalWidth;
+    canvas.height = finalHeight;

     if (ctx) {
         ctx.setTransform(pixelRatio, 0, 0, pixelRatio, 0, 0);
         ctx.imageSmoothingQuality = "high";

         ctx.save();

         if (circularCrop) {
-            canvas.width = ccrop.width;
-            canvas.height = ccrop.height;
-
             ctx.beginPath();

Also applies to: 103-105

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

Extra white space in cropped image
1 participant