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

LNK-3055: Update measure eval to use 3.12 CQFramework libraries #498

Merged

Conversation

c-schuler
Copy link
Contributor

@c-schuler c-schuler commented Oct 7, 2024

🛠 Description of Changes

  • Updated dependency for clinical-reasoning to 3.12
  • Updated dependency for HAPI FHIR to 7.4 (required by v3.12 of clinical-reasoning)

These updates are needed to enable debug logging within the CQL Engine.

🧪 Testing Performed

Tested locally with unit tests developed on another branch. Please conduct local tests to ensure functionality.

NOTE: the logging level must be set to DEBUG in order to see the log messages. This can easily be achieved through the addition of a logback.xml in the resources directory.

Here is an example logback.xml:

<configuration>

  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <!-- encoders are assigned the type
         ch.qos.logback.classic.encoder.PatternLayoutEncoder by default -->
    <encoder>
      <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} -%kvp- %msg%n</pattern>
    </encoder>
  </appender>

  <root level="debug">
    <appender-ref ref="STDOUT" />
  </root>
</configuration>

Summary by CodeRabbit

  • New Features

    • Added support for the Apache Commons Collections library, enhancing data structure capabilities.
  • Updates

    • Upgraded cqf-fhir library version from 3.0.0 to 3.12.0.
    • Upgraded hapi-fhir library version from 7.0.0 to 7.4.0.
  • Bug Fixes

    • Updated exception handling to utilize the latest version of CollectionUtils, ensuring improved functionality.

Copy link
Contributor

coderabbitai bot commented Oct 7, 2024

Walkthrough

This pull request introduces updates to the dependency management in the pom.xml files of two Java projects, measureeval and a general Java project. A new dependency for commons-collections4 version 4.4 is added, and existing dependencies for cqf-fhir and hapi-fhir are upgraded to versions 3.12.0 and 7.4.0, respectively. Additionally, the ExceptionHandlers class is updated to import CollectionUtils from the new commons-collections4 package, ensuring compatibility with the updated library.

Changes

File Path Change Summary
Java/measureeval/pom.xml Added dependency for commons-collections4 version 4.4.
Java/measureeval/src/main/java/com/lantanagroup/link/measureeval/controllers/ExceptionHandlers.java Updated import statement for CollectionUtils from org.apache.commons.collections to org.apache.commons.collections4.
Java/pom.xml Upgraded cqf-fhir from 3.0.0 to 3.12.0 and hapi-fhir from 7.0.0 to 7.4.0. Added dependency for commons-collections4 version 4.4.

Possibly related PRs

Suggested reviewers

  • amphillipsLGC

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 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
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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0ad5152 and 585e3f5.

📒 Files selected for processing (3)
  • Java/measureeval/pom.xml (1 hunks)
  • Java/measureeval/src/main/java/com/lantanagroup/link/measureeval/controllers/ExceptionHandlers.java (1 hunks)
  • Java/pom.xml (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • Java/measureeval/src/main/java/com/lantanagroup/link/measureeval/controllers/ExceptionHandlers.java
🧰 Additional context used
🔇 Additional comments (3)
Java/pom.xml (3)

114-119: LGTM! Verify usage of commons-collections4 in the project.

The addition of the commons-collections4 dependency (version 4.4) is a good choice, as it's a widely used and well-maintained Apache library.

Please ensure that this new dependency is actually used in the project. Run the following script to check for its usage:

#!/bin/bash
# Description: Check for usage of commons-collections4 in the project

# Test: Search for imports from org.apache.commons.collections4
echo "Searching for imports from commons-collections4:"
rg --type java 'import org\.apache\.commons\.collections4'

# Test: Look for usage of specific classes from commons-collections4
echo "Searching for usage of common classes from commons-collections4:"
rg --type java '(CollectionUtils|MapUtils|ListUtils|SetUtils)'

If there are no results, consider removing this dependency to avoid unnecessary bloat in the project.


23-24: LGTM! Verify compatibility with the rest of the project.

The updates to cqf-fhir.version (3.0.0 to 3.12.0) and hapi-fhir.version (7.0.0 to 7.4.0) align with the PR objectives. These are significant version changes, especially for cqf-fhir.

Please ensure that these updates are compatible with the rest of the project. Run the following script to check for any potential conflicts or issues:

✅ Verification successful

Verified! The updates to cqf-fhir.version (3.0.0 to 3.12.0) and hapi-fhir.version (7.0.0 to 7.4.0) are actively used in the codebase with no apparent compatibility issues or outstanding comments.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for potential compatibility issues with the updated dependencies

# Test: Search for usages of classes or methods from cqf-fhir and hapi-fhir libraries
echo "Searching for cqf-fhir and hapi-fhir usages:"
rg --type java -i '(import|extends|implements).*?(cqf|hapi)\.fhir'

# Test: Check if there are any TODO or FIXME comments related to these libraries
echo "Checking for TODO or FIXME comments related to cqf-fhir or hapi-fhir:"
rg --type java -i '(TODO|FIXME).*?(cqf|hapi)\.fhir'

# Test: Look for any custom implementations or overrides of cqf-fhir or hapi-fhir classes
echo "Searching for custom implementations or overrides:"
rg --type java -i 'class.*extends.*?(cqf|hapi)\.fhir'

Length of output: 1786


Line range hint 120-141: Verify compatibility of all modules with updated BOMs.

The hapi-fhir-bom and cqf-fhir-bom dependencies are implicitly updated through the property changes made earlier. This is a good practice for version management.

Please ensure that all modules using these BOMs are compatible with the new versions. Run the following script to check for potential issues:

Review the results to ensure that all modules are compatible with the updated versions.

✅ Verification successful

Please run the following corrected script to verify compatibility issues with the updated BOMs:

[/run_scripts]


Java/measureeval/pom.xml Show resolved Hide resolved
@seanmcilvenna
Copy link
Contributor

@smailliwcs when you have a sec... please give this a glance.

@c-schuler c-schuler merged commit 286b667 into dev Oct 22, 2024
20 of 21 checks passed
@c-schuler c-schuler deleted the LNK-3055-Update-measure-eval-to-use-3.12-CQFramework-libraries branch October 22, 2024 18:03
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