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(service-portal): Change date check #17605

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

magnearun
Copy link
Contributor

@magnearun magnearun commented Jan 22, 2025

What

We want to show delegations that expire today

Why

Users can select today as expire date, expecting it to expire at end of day

Screenshots / Gifs

Attach Screenshots / Gifs to help reviewers understand the scope of the pull request

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Formatting passes locally with my changes
  • I have rebased against main before asking for a review

Summary by CodeRabbit

  • Bug Fixes
    • Improved date expiration logic to more accurately determine delegation expiration status.
    • Enhanced time-based validation using a more precise method for date comparisons.

we want to show delegations that expire today
@magnearun magnearun requested a review from a team as a code owner January 22, 2025 11:43
Copy link
Contributor

coderabbitai bot commented Jan 22, 2025

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

warning [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
warning eslint > @humanwhocodes/[email protected]: Use @eslint/config-array instead
warning eslint > @humanwhocodes/config-array > @humanwhocodes/[email protected]: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > [email protected]: Rimraf versions prior to v4 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > [email protected]: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > rimraf > glob > [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning jest > @jest/core > jest-runtime > [email protected]: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > jest-config > [email protected]: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/reporters > [email protected]: Glob versions prior to v9 are no longer supported
warning jest > @jest/core > @jest/transform > babel-plugin-istanbul > test-exclude > [email protected]: Glob versions prior to v9 are no longer supported
warning storybook > @storybook/cli > puppeteer-core > [email protected]: Rimraf versions prior to v4 are no longer supported
warning storybook > @storybook/cli > puppeteer-core > rimraf > [email protected]: Glob versions prior to v9 are no longer supported
warning storybook > @storybook/cli > jscodeshift > temp > [email protected]: Rimraf versions prior to v4 are no longer supported
warning storybook > @storybook/cli > jscodeshift > temp > rimraf > [email protected]: Glob versions prior to v9 are no longer supported
warning storybook > @storybook/cli > jscodeshift > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
warning storybook > @storybook/cli > tempy > del > [email protected]: Rimraf versions prior to v4 are no longer supported
warning storybook > @storybook/cli > jscodeshift > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
warning storybook > @storybook/cli > jscodeshift > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
warning react-native > @react-native/codegen > [email protected]: Glob versions prior to v9 are no longer supported
warning react-native > @react-native/community-cli-plugin > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning react-native > @react-native-community/cli > @react-native-community/cli-tools > [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
warning react-native > @react-native/community-cli-plugin > @react-native/dev-middleware > @rnx-kit/chromium-edge-launcher > [email protected]: Rimraf versions prior to v4 are no longer supported
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
warning react-native > @react-native/community-cli-plugin > @react-native/metro-babel-transformer > @react-native/babel-preset > @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
warning next-auth > [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning next-auth > [email protected]: this version is no longer supported
warning next-auth > @next-auth/typeorm-legacy-adapter > typeorm > [email protected]: Glob versions prior to v9 are no longer supported
warning @nx/next > @nx/webpack > stylus > [email protected]: Glob versions prior to v9 are no longer supported
warning @nx/next > @nx/webpack > webpack-dev-server > [email protected]: Rimraf versions prior to v4 are no longer supported
warning @nx/next > @nx/webpack > fork-ts-checker-webpack-plugin > [email protected]: this will be v4
warning @nx/next > @nx/webpack > webpack-dev-server > webpack-dev-middleware > [email protected]: this will be v4
warning workspace-aggregator-711f4c80-afe3-4016-93ff-c731424f066e > [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.

Walkthrough

The pull request modifies the isDateExpired function in the AccessCard.tsx component by incorporating the startOfDay function from the date-fns library. This change updates the logic for determining date expiration by comparing dates to the start of the current day, refining how delegation expiration is evaluated. The overall structure and flow of the AccessCard component remain unchanged.

Changes

File Change Summary
libs/portals/shared-modules/delegations/src/components/access/AccessCard.tsx - Added import for startOfDay from date-fns
- Modified isDateExpired function to use startOfDay for date comparison

Suggested labels

automerge

Suggested reviewers

  • disaerna

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cdf9443 and 06020be.

📒 Files selected for processing (1)
  • libs/portals/shared-modules/delegations/src/components/access/AccessCard.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • libs/portals/shared-modules/delegations/src/components/access/AccessCard.tsx

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.

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
Contributor

@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 (1)
libs/portals/shared-modules/delegations/src/components/access/AccessCard.tsx (1)

30-30: Improve type safety of the date expiration check.

While the logic change correctly fixes the date comparison, we can improve type safety:

-const isDateExpired = (date?: string | null) => date && new Date(date) < startOfDay(new Date())
+const isDateExpired = (date?: string | null): boolean => {
+  if (!date) return false;
+  const expirationDate = new Date(date);
+  return !isNaN(expirationDate.getTime()) && expirationDate < startOfDay(new Date());
+}

This change:

  • Adds explicit return type
  • Validates date parsing
  • Makes the logic more readable
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 305b983 and cdf9443.

📒 Files selected for processing (1)
  • libs/portals/shared-modules/delegations/src/components/access/AccessCard.tsx (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
libs/portals/shared-modules/delegations/src/components/access/AccessCard.tsx (1)

Pattern libs/**/*: "Confirm that the code adheres to the following:

  • Reusability of components and hooks across different NextJS apps.
  • TypeScript usage for defining props and exporting types.
  • Effective tree-shaking and bundling practices."
🔇 Additional comments (2)
libs/portals/shared-modules/delegations/src/components/access/AccessCard.tsx (2)

21-21: LGTM! Import follows tree-shaking best practices.

The direct import from date-fns/startOfDay ensures optimal tree-shaking, consistent with the existing date-fns imports.


30-30: Consider timezone implications in date comparisons.

The current implementation uses local timezone for date comparisons. Depending on your requirements, you might want to:

  1. Use UTC for consistent date comparisons across timezones
  2. Consider the user's timezone when determining expiration

Let's verify if there are any timezone-related issues reported:

✅ Verification successful

The current implementation using local timezone is acceptable for client-side expiration checks.

The code consistently uses the browser's local timezone which is typically the desired behavior for user-facing expiration checks. However, consider documenting this assumption and if multi-timezone support becomes a requirement:

  1. Store dates in UTC format on the server
  2. Add explicit timezone handling where needed using date-fns-tz
  3. Include timezone information in the date string when comparing across zones
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for timezone-related discussions or issues
rg -i "timezone|tz|utc" --type ts

Length of output: 66169


Script:

#!/bin/bash
# Search for date-fns imports and usage
rg -i "from 'date-fns'" --type ts -A 2

Length of output: 470

@magnearun magnearun changed the title Fix(service-portal): Change date check fix(service-portal): Change date check Jan 22, 2025
Copy link
Member

@GunnlaugurG GunnlaugurG left a comment

Choose a reason for hiding this comment

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

LGTM

@datadog-island-is
Copy link

datadog-island-is bot commented Jan 22, 2025

Datadog Report

All test runs de10d14 🔗

10 Total Test Services: 0 Failed, 10 Passed
🔻 Test Sessions change in coverage: 1 decreased (-0.01%), 2 increased, 90 no change

Test Services
This report shows up to 10 services
Service Name Failed Known Flaky New Flaky Passed Skipped Total Time Code Coverage Change Test Service View
air-discount-scheme-backend 0 0 0 63 0 22.18s 1 no change Link
air-discount-scheme-web 0 0 0 2 0 6.55s 1 no change Link
api 0 0 0 4 0 2.58s 1 no change Link
api-domains-air-discount-scheme 0 0 0 6 0 17.6s 1 no change Link
api-domains-auth-admin 0 0 0 18 0 11.05s 1 no change Link
application-system-api 0 0 0 46 0 2m 42.01s 1 no change Link
application-template-api-modules 0 0 0 118 0 2m 7.13s 1 decreased (-0.01%) Link
application-ui-shell 0 0 0 74 0 33.17s 1 no change Link
auth-admin-web 0 0 0 1 0 7.58s 1 no change Link
auth-api-lib 0 0 0 20 0 24.73s 1 no change Link

🔻 Code Coverage Decreases vs Default Branch (1)

  • application-template-api-modules - jest 30.02% (-0.01%) - Details

@magnearun magnearun enabled auto-merge January 22, 2025 14:30
Copy link

codecov bot commented Jan 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 35.57%. Comparing base (bb52c30) to head (06020be).
Report is 6 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #17605   +/-   ##
=======================================
  Coverage   35.57%   35.57%           
=======================================
  Files        7030     7030           
  Lines      150489   150489           
  Branches    42973    42973           
=======================================
+ Hits        53536    53538    +2     
+ Misses      96953    96951    -2     
Flag Coverage Δ
air-discount-scheme-backend 48.15% <ø> (ø)
air-discount-scheme-web 0.00% <ø> (ø)
api 3.33% <ø> (ø)
api-domains-air-discount-scheme 37.90% <ø> (ø)
api-domains-auth-admin 48.49% <ø> (ø)
application-system-api 38.67% <ø> (+<0.01%) ⬆️
application-template-api-modules 27.56% <ø> (-0.02%) ⬇️
application-ui-shell 22.00% <ø> (ø)
auth-admin-web 2.43% <ø> (ø)
auth-shared 75.00% <ø> (ø)
contentful-apps 4.56% <ø> (ø)
financial-aid-backend 51.38% <ø> (ø)
icelandic-names-registry-backend 54.44% <ø> (ø)
judicial-system-api 20.07% <ø> (ø)
judicial-system-backend 55.81% <ø> (ø)
judicial-system-message-handler 47.89% <ø> (ø)
judicial-system-scheduler 71.24% <ø> (ø)
judicial-system-web 27.97% <ø> (ø)
license-api 42.97% <ø> (+0.05%) ⬆️
services-auth-admin-api 52.47% <ø> (ø)
services-auth-delegation-api 58.47% <ø> (ø)
services-auth-ids-api 52.52% <ø> (+0.02%) ⬆️
services-auth-public-api 49.36% <ø> (ø)
services-sessions 65.33% <ø> (ø)
services-university-gateway 49.35% <ø> (-0.09%) ⬇️
services-user-notification 46.53% <ø> (ø)
services-user-profile 56.92% <ø> (+0.06%) ⬆️
skilavottord-ws 23.97% <ø> (ø)
web 2.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bb52c30...06020be. Read the comment docs.

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.

3 participants