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

Completed the datepicker feature in user standup updates and fixed the hover issue on dates #851

Open
wants to merge 12 commits into
base: develop
Choose a base branch
from

Conversation

ANKIT9761
Copy link

@ANKIT9761 ANKIT9761 commented Sep 24, 2024

Issue on standup dates

Date: 24-09-2024

Developer Name: Ankit Kanyal


Issue Ticket Number

#830

Description

So I have added a datepicker in user standup update section when clicked the user is automatically scrolled to that particular standup date.Also I have fixed hover issues when user hover over standup dates .Previously when user hover over any date hover effect is applied to entire row.

Documentation Updated?

  • Yes
  • No

Under Feature Flag

  • Yes
  • No

Database Changes

  • Yes
  • No

Breaking Changes

  • Yes
  • No

Development Tested?

  • Yes
  • No

Screenshots

Screenshot 1

image

standup-demo.mp4

Test Coverage

Screenshot 1

Group tests are passing.
image

image

Additional Notes

Summary by CodeRabbit

  • New Features

    • Introduced a dynamic date picker in the table header that lets users select a date, automatically scrolling the table to bring the corresponding date column into view.
  • Style

    • Updated hover interaction so that individual table cells highlight on hover instead of the entire row, providing a more focused user experience.

Copy link
Member

@vinit717 vinit717 left a comment

Choose a reason for hiding this comment

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

Write test for your changes

Copy link
Member

@vinit717 vinit717 left a comment

Choose a reason for hiding this comment

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

why there is too much changes as your task is related to only standup

@ANKIT9761
Copy link
Author

ANKIT9761 commented Sep 27, 2024

@vinit717

why there is too much changes as your task is related to only standup

After making changes there was an update on develop branch so as stated in contributing.md I pulled those changes and rebased it as we were told to do in the readme.

@vinit717 vinit717 changed the base branch from develop to fix/conflict September 27, 2024 17:06
@vinit717 vinit717 changed the base branch from fix/conflict to develop September 27, 2024 17:06
@ANKIT9761 ANKIT9761 requested a review from vinit717 September 27, 2024 19:37
Copy link

coderabbitai bot commented Feb 24, 2025

Walkthrough

The changes introduce enhancements for date handling and scrolling functionality. In the test file, new functions for counting Sundays and calculating scroll position are added alongside test cases to validate correct scrolling behavior based on a selected date. In the main script, the table header is updated with a dynamic date picker and a new scroll-to-date function is implemented. Additionally, the hover effect in styles is refined by shifting from row-based to cell-based interactions.

Changes

File(s) Change Summary
__tests__/standup/standup.test.js
standup/script.js
Added new date handling functions: both files now include countSundays; test file adds calculateScrollPosition with corresponding test cases, and the script adds a date picker element with an event listener triggering scrollToSelectedDate to scroll the table based on the selected date.
standup/style.css Removed the row hover effect (tr:hover) and implemented an individual cell hover effect (td:hover) applying a specific background color (var(--dark-gray-color)).

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DatePicker
    participant ScrollFunction
    participant CountSundays
    participant Table

    User->>DatePicker: Select date
    DatePicker->>ScrollFunction: Trigger change event with date
    ScrollFunction->>CountSundays: Calculate Sundays between dates
    CountSundays-->>ScrollFunction: Return count
    ScrollFunction->>Table: Compute and apply scroll position
Loading

Poem

In the code garden, I hop with glee,
Adding functions like carrots for all to see.
A date picker sprouted, neat and bright,
Scrolls the table just right – what a sight!
With each Sunday counted, my joy takes flight.
🐇💻 Happy coding under the moonlit byte!

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

🪧 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: 0

🧹 Nitpick comments (3)
standup/script.js (1)

385-420: Consider adding error handling for invalid dates.

The scrollToSelectedDate function should handle potential edge cases:

  • Invalid date strings
  • Null or undefined values
 function scrollToSelectedDate(date) {
+  if (!date) return;
   const selectedDate = new Date(date);
+  if (isNaN(selectedDate.getTime())) return;
   selectedDate.setHours(0, 0, 0, 0);

   if (selectedDate < startDate || selectedDate > endDate) {
     return;
   }
__tests__/standup/standup.test.js (2)

191-224: Consider reducing test flakiness.

The test relies on fixed timeouts which could lead to flaky behavior. Consider using more reliable waiting mechanisms.

-    await page.waitForTimeout(1000);
+    await page.waitForFunction(() => {
+      const container = document.getElementById('table-container');
+      return container.scrollLeft > 0;
+    });

226-259: Consider adding more edge cases.

The test could be expanded to cover additional scenarios:

  • Invalid date strings
  • Null or undefined values
  • Dates before the start date
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ce6be97 and f297a49.

📒 Files selected for processing (3)
  • __tests__/standup/standup.test.js (2 hunks)
  • standup/script.js (2 hunks)
  • standup/style.css (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: test
  • GitHub Check: Analyze (javascript)
🔇 Additional comments (4)
standup/style.css (1)

158-160: LGTM! The hover effect is now correctly scoped to individual cells.

The changes successfully address the hover issue mentioned in the PR objectives by shifting from row-based to cell-based hover interactions.

standup/script.js (2)

124-143: LGTM! The datepicker implementation follows best practices.

The changes align with past review feedback by:

  • Creating separate DOM elements instead of using string HTML.
  • Using proper element hierarchy and styling.

146-149: LGTM! Event handling is properly implemented.

The event listener is correctly set up to handle date selection and trigger scrolling.

__tests__/standup/standup.test.js (1)

25-52: LGTM! The utility functions are well-implemented.

The functions correctly handle:

  • Sunday counting logic
  • Scroll position calculation

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.

4 participants