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

[organization action items] updated OrganizationActionItem screen #2160

Conversation

Alfredoeb9
Copy link

@Alfredoeb9 Alfredoeb9 commented Aug 8, 2024

…fix buttons on mobile screen

updated OrganizationActionItems screen to fix button and dropdown menus on mobile screens as buttons were off screen during tablet - mobile

What kind of change does this PR introduce?

bugfix

Issue Number:

Fixes #2094

Did you add tests for your changes?

No, not needed only changed css.

Summary

updated OrganizationActionItems screen to fix button and dropdown menus on mobile screens as buttons were off screen during tablet - mobile

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • New Features

    • Improved button layout and alignment for a better user experience.
    • Buttons are now stacked vertically for enhanced usability.
    • Extended the duration of mock data for pledges to accommodate longer-term goals.
  • Style

    • Updated CSS for button containers to center and better organize buttons visually.
    • Applied new styling properties to enhance the overall aesthetics of the button blocks.

…fix buttons on mobile screen

updated OrganizationActionItems screen to fix button and dropdown menus on mobile screens
as buttons were off screen during tablet - mobile
Copy link

coderabbitai bot commented Aug 8, 2024

Important

Review skipped

Review was skipped due to path filters

Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes made to the OrganizationActionItems screen focus on enhancing the layout of buttons to ensure they are properly centered and organized, particularly for mobile devices. CSS updates improve the visual alignment and usability of buttons, addressing issues of elements being out of bounds. Minor JSX adjustments streamline class name handling without altering functionality.

Changes

Files Change Summary
src/screens/OrganizationActionItems/*.css, src/screens/OrganizationActionItems/OrganizationActionItems.tsx Updated CSS for button alignment and layout, and adjusted class name assignment in JSX.
src/screens/FundCampaignPledge/PledgesMocks.ts Modified endDate in MOCKS to extend the duration of pledges by ten years.

Assessment against linked issues

Objective Addressed Explanation
Ensure create button is within parent container (#2094)
Improve button layout for mobile display (#2094)

Poem

In a cozy nook where buttons play,
The rabbit hops and fluffs away.
Centered well, they shine so bright,
Mobile screens now bring delight!
With a wiggle and a hop, hooray!
Usability's here to stay! 🐇✨


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

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

github-actions bot commented Aug 8, 2024

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if these conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold
  3. Merge conflicts

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3d4a87e and 357bf83.

Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
Files selected for processing (2)
  • src/screens/OrganizationActionItems/OrganizationActionItems.module.css (3 hunks)
  • src/screens/OrganizationActionItems/OrganizationActionItems.tsx (1 hunks)
Files skipped from review due to trivial changes (1)
  • src/screens/OrganizationActionItems/OrganizationActionItems.tsx
Additional comments not posted (3)
src/screens/OrganizationActionItems/OrganizationActionItems.module.css (3)

14-15: LGTM! Centering buttons improves alignment.

The addition of justify-content: center; and align-items: center; in the .btnsContainer class effectively centers the buttons within the container, enhancing the layout.


155-159: LGTM! Mobile layout adjustments enhance usability.

The changes within the media query for .btnsContainer and .btnsBlock are well-suited for mobile screens, ensuring a vertical stack of elements for better usability.


160-162: LGTM! Dropdown toggle space utilization is improved.

Setting flex-grow: 1; for .btnsContainer .btnsBlock .dropdownToggle ensures it expands to fill available space, enhancing layout consistency.

coderabbitai[bot]
coderabbitai bot previously approved these changes Aug 8, 2024
@Alfredoeb9
Copy link
Author

looks like test src/screens/FundCampaignPledge/FundCampaignPledge.test.tsx is failing, not sure why as I only changed css on OrganizationActionItems Screen so this error did not come from this PR.

@Cioppolo14
Copy link

@Alfredoeb9 Please fix the failing tests.

@Alfredoeb9
Copy link
Author

Alfredoeb9 commented Aug 8, 2024

@Cioppolo14 looks like last major file changes on these files were from https://github.com/PalisadoesFoundation/talawa-admin/pull/2064/files from user @GlenDsza.

Commit: src/screens/FundCampaignPledge/FundCampaignPledge.tsx

Also seeing a new PR: #2163

I suggest teaming up with GlenDsza as this was their task.

Those changes are my roadblock, my changes on this PR do not affect unit test from errors seeing above in this PR.

@GlenDsza
Copy link

GlenDsza commented Aug 9, 2024

@Alfredoeb9 the issue could be resolved by changing the year values of endDate on following line

Set the endDate to something in far distant future endDate: "2034-08-08". I have changed this in my recent PR but it might take time to get merged as the size of changes is vast

@Alfredoeb9
Copy link
Author

Alfredoeb9 commented Aug 9, 2024

@GlenDsza copy that! Since changes are made in your PR, I'll wait until your changes have integrated so there is no conflict when my PR is merged. Thank you for the follow up!

@Cioppolo14 We should wait on this PR merge until @GlenDsza is completely merged to avoid any conflict.

@Alfredoeb9
Copy link
Author

@Cioppolo14 seeing #2163 has been merged. Can we update this PR branch with the latest changes. All tests should be good now.

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

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 357bf83 and 8c52327.

Files selected for processing (1)
  • src/screens/FundCampaignPledge/PledgesMocks.ts (1 hunks)
Additional comments not posted (1)
src/screens/FundCampaignPledge/PledgesMocks.ts (1)

25-25: Verify the impact of the endDate change on tests.

The endDate has been extended to 2034-08-08. Ensure that this change aligns with the intended testing scenarios and doesn't inadvertently affect test outcomes.

coderabbitai[bot]
coderabbitai bot previously approved these changes Aug 17, 2024
Copy link

codecov bot commented Aug 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.55%. Comparing base (47bdf2b) to head (af91630).
Report is 29 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #2160   +/-   ##
========================================
  Coverage    97.55%   97.55%           
========================================
  Files          244      244           
  Lines         6939     6939           
  Branches      2000     2000           
========================================
  Hits          6769     6769           
  Misses         155      155           
  Partials        15       15           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Alfredoeb9
Copy link
Author

@Cioppolo14 @palisadoes PR is ready for review and to be merged 👍.

@palisadoes
Copy link
Contributor

  1. Please add a video to show how this works.
  2. We don't expect users to be running Admin on a mobile phone, but on a tablet where the options will be more usable. This PR may not be suitable for our needs.

Copy link
Contributor

@palisadoes palisadoes left a comment

Choose a reason for hiding this comment

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

  1. Please add a video to show how this works.
  2. We don't expect users to be running Admin on a mobile phone, but on a tablet where the options will be more usable. This PR may not be suitable for our needs.

@Alfredoeb9
Copy link
Author

Sure will upload video right now

Copy link

github-actions bot commented Sep 9, 2024

This pull request did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please verify it has no conflicts with the develop branch and rebase if needed. Mention it now if you need help or give permission to other people to finish your work.

@github-actions github-actions bot added the no-pr-activity No pull request activity label Sep 9, 2024
@palisadoes
Copy link
Contributor

Closing. Inactivity.

@palisadoes palisadoes closed this Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-pr-activity No pull request activity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants