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: uncaught exception in case of missing source #747

Merged
merged 3 commits into from
Dec 18, 2024

Conversation

rosado
Copy link
Collaborator

@rosado rosado commented Dec 16, 2024

What type of PR is this? (check all applicable)

  • Bug Fix

Description

Sometimes the 'source' in request object is not present and we end up accessing a member (startDate) in undefined value.

Added/updated tests?

  • Yes

Summary by CodeRabbit

  • Bug Fixes

    • Improved error handling for cases where the source object may be undefined, ensuring robust behaviour of the middleware.
  • Tests

    • Added a new test case to verify the middleware's behaviour when an invalid source key is provided, enhancing test coverage for edge cases.

@rosado rosado added the bug Something isn't working label Dec 16, 2024
Copy link
Contributor

coderabbitai bot commented Dec 16, 2024

Walkthrough

The pull request focuses on enhancing the error handling and robustness of the setNoticesFromSourceKey middleware function in the dataset overview module. The changes primarily address potential issues with undefined source objects and improve the handling of start dates. A new unit test has been added to verify the middleware's behaviour when dealing with invalid source keys, expanding the test coverage for edge cases in the dataset overview functionality.

Changes

File Change Summary
src/middleware/datasetOverview.middleware.js - Improved handling of startDate when source is undefined
- Added optional chaining for logging
- Enhanced error handling for invalid start dates
test/unit/middleware/datasetOverview.middleware.test.js - Added new test case for handling missing source keys
- Verified graceful handling of invalid source key scenarios

Sequence Diagram

sequenceDiagram
    participant Middleware
    participant Request
    participant Source
    
    Middleware->>Source: Check source exists
    alt Source exists
        Source-->>Middleware: Retrieve start date
        Middleware->>Middleware: Validate start date
    else Source is undefined
        Middleware->>Middleware: Set startDate to undefined
        Middleware->>Request: Proceed without setting notices
    end
Loading

Possibly related PRs

Poem

🐰 A middleware's tale of grace,
Where undefined meets its embrace
Source keys dance, dates take flight
Error handling shines so bright
Robust code hops with delight! 🌟

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request.


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

github-actions bot commented Dec 16, 2024

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 70.56% 5207 / 7379
🔵 Statements 70.56% 5207 / 7379
🔵 Functions 68.72% 211 / 307
🔵 Branches 83.21% 689 / 828
File Coverage
File Stmts Branches Functions Lines Uncovered Lines
Changed Files
src/middleware/datasetOverview.middleware.js 69.46% 67.5% 28.57% 69.46% 11-31, 44-96, 117-121, 199
Generated in workflow #508 for commit 58b4c75 by the Vitest Coverage Report Action

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 (2)
src/middleware/datasetOverview.middleware.js (1)

129-134: The fix correctly handles missing source, but could be more descriptive

The changes properly address the uncaught exception when source is missing, but we could improve the error handling further.

Consider enhancing the error logging and restructuring the checks:

-    const startDate = source ? new Date(source.startDate) : undefined
-
-    if (!startDate || startDate.toString() === 'Invalid Date') {
-      logger.warn('Invalid start date encountered', {
-        type: types.DataValidation,
-        startDate: source?.startDate
-      })
+    if (!source) {
+      logger.warn('Source object is missing', {
+        type: types.DataValidation,
+        sourceKey
+      })
+      return next()
+    }
+
+    const startDate = new Date(source.startDate)
+    if (startDate.toString() === 'Invalid Date') {
+      logger.warn('Invalid start date format', {
+        type: types.DataValidation,
+        startDate: source.startDate
+      })
       return next()
     }
test/unit/middleware/datasetOverview.middleware.test.js (1)

207-213: Test coverage could be more comprehensive

The test correctly verifies the handling of missing source, but we could enhance the coverage.

Consider adding these additional test cases:

it('should handle source without startDate gracefully', () => {
  const reqWithEmptySource = {
    ...req,
    foobar: {}  // source without startDate
  }
  setNoticesFromSourceKey('foobar')(reqWithEmptySource, res, () => {})
  expect(reqWithEmptySource.notice).toBeUndefined()
})

it('should handle invalid startDate format gracefully', () => {
  const reqWithInvalidDate = {
    ...req,
    foobar: { startDate: 'invalid-date' }
  }
  setNoticesFromSourceKey('foobar')(reqWithInvalidDate, res, () => {})
  expect(reqWithInvalidDate.notice).toBeUndefined()
})
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a0b54a8 and 159b9bc.

📒 Files selected for processing (2)
  • src/middleware/datasetOverview.middleware.js (1 hunks)
  • test/unit/middleware/datasetOverview.middleware.test.js (1 hunks)

@rosado rosado self-assigned this Dec 16, 2024
@eveleighoj eveleighoj temporarily deployed to submit-pr-747 December 17, 2024 08:23 Inactive
@rosado rosado merged commit a93d20a into main Dec 18, 2024
5 checks passed
@rosado rosado deleted the rosado/NOJIRA-source-start-date-fix branch December 18, 2024 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants