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

CCCT-580 || Payment card tap issue in delivery progress screen #2922

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

Conversation

j13panchal
Copy link

Solved tap issue on payment card in delivery progress screen

Summary

https://dimagi.atlassian.net/browse/CCCT-580

Feature Flag

Product Description

PR Checklist

  • If I think the PR is high risk, "High Risk" label is set
  • I have confidence that this PR will not introduce a regression for the reasons below
  • Do we need to enhance manual QA test coverage ? If yes, "QA Note" label is set correctly
  • Does the PR introduce any major changes worth communicating ? If yes, "Release Note" label is set and a "Release Note" is specified in PR description.

Automated test coverage

Safety story

Solved tap issue on payment card in delivery progress screen
Copy link

coderabbitai bot commented Dec 13, 2024

📝 Walkthrough

Walkthrough

The pull request introduces modifications to two primary files: connect_delivery_progress_item.xml and ConnectDeliveryProgressReportAdapter.java. In the XML layout file, a new ID rootView is added to the CardView, which now includes several new attributes such as clickable, focusable, and various shadow properties. The existing rootView ID is removed, indicating a restructuring of the layout hierarchy. Additionally, the IDs for tvApproved, tvDeliveryTotalAmount, and tvRemaining are updated, with changes to their layout parameters to enhance interactivity and visual presentation. The ImageView for imgArrowForward retains its ID but has its layout width explicitly defined.

In the Java adapter class, the click event handling has been updated to respond to clicks on the entire rootView instead of just the arrow image. This change maintains the same method signature for the click listener, which continues to invoke the onClick method of the DeliveryItemOnClickListener interface with the delivery name as a parameter. No other changes to logic or error handling are present.

Possibly related PRs

  • QA-7221 || Learning Delivery Progress Screen Bugs #2915: The changes in this PR involve modifications to layout files and UI components, which may relate to the overall structure and presentation of the delivery progress screen, similar to the changes made in the main PR's layout file.

Suggested reviewers

  • OrangeAndGreen

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. (Experiment)
  • @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: 0

🧹 Outside diff range and nitpick comments (3)
app/res/layout/connect_delivery_progress_item.xml (3)

11-14: Consider using dp units for shadow properties.

Shadow properties should use dp units instead of raw numbers for consistent appearance across different screen densities.

-    android:shadowDx="30"
-    android:shadowDy="30"
-    android:shadowRadius="50"
+    android:shadowDx="8dp"
+    android:shadowDy="8dp"
+    android:shadowRadius="12dp"

Line range hint 77-93: Consider extracting dimensions to dimens.xml.

Hard-coded dimensions like text sizes, margins, and paddings should be defined in dimens.xml for better maintainability and consistency.

Example structure for dimens.xml:

<resources>
    <!-- Text sizes -->
    <dimen name="text_size_small">11sp</dimen>
    <dimen name="text_size_medium">12sp</dimen>
    
    <!-- Margins -->
    <dimen name="margin_small">3dp</dimen>
    <dimen name="margin_medium">6dp</dimen>
</resources>

Also applies to: 131-139


Line range hint 154-161: Verify RTL support for right margin.

The android:layout_marginRight attribute should be replaced with android:layout_marginEnd for proper RTL support.

-    android:layout_marginRight="10dp"
+    android:layout_marginEnd="10dp"
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 96a1c74 and 8b810c3.

📒 Files selected for processing (2)
  • app/res/layout/connect_delivery_progress_item.xml (4 hunks)
  • app/src/org/commcare/adapters/ConnectDeliveryProgressReportAdapter.java (1 hunks)
🔇 Additional comments (2)
app/src/org/commcare/adapters/ConnectDeliveryProgressReportAdapter.java (1)

51-53: LGTM! Improved tap target accessibility.

Moving the click listener from the arrow icon to the entire card view (rootView) improves accessibility by:

  • Providing a larger tap target
  • Making the interaction more intuitive
  • Following material design guidelines for card interactions
app/res/layout/connect_delivery_progress_item.xml (1)

4-16: LGTM! Proper implementation of material design card interaction.

The CardView is now properly configured for touch interaction with:

  • Clickable and focusable properties
  • Ripple effect feedback via selectableItemBackground
  • Visual elevation through shadows

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.

2 participants