Skip to content
This repository was archived by the owner on Apr 1, 2026. It is now read-only.

Devops/update logging to new standard#576

Merged
MikeNeilson merged 2 commits into
mainfrom
devops/update-logging-to-new-standard
Nov 4, 2025
Merged

Devops/update logging to new standard#576
MikeNeilson merged 2 commits into
mainfrom
devops/update-logging-to-new-standard

Conversation

@MikeNeilson

Copy link
Copy Markdown
Collaborator

Problem Description

Logging statement style and exception naming was inconsistent

Solution

Update statement style and naming to match main code

Depends on #575

how you tested the change

No logic changes. (Minor variations on how logging is handled).

Where the following done:

  • Tests. Check all that apply:
    • Unit tests created or modified that run during ant test.
    • Integration tests created or modified that run during integration testing
      (Formerly called regression tests.)
    • Test procedure descriptions for manual testing
  • Was relevant documentation updated?
  • Were relevant config element (e.g. XML data) updated as appropriate

If you aren't sure leave unchecked and we will help guide you to want needs changing where.

@MikeNeilson MikeNeilson requested a review from a team October 26, 2025 14:31
@MikeNeilson

Copy link
Copy Markdown
Collaborator Author

sorry, one logic change, method computations depends on was remove, elements were replaced.

@MikeNeilson MikeNeilson force-pushed the devops/update-logging-to-new-standard branch from b6624f7 to 9927c83 Compare November 2, 2025 14:37
@sonarqubecloud

sonarqubecloud Bot commented Nov 2, 2025

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
25.9% Coverage on New Code (required ≥ 30%)

See analysis details on SonarQube Cloud

@MikeNeilson MikeNeilson merged commit fee91bc into main Nov 4, 2025
9 of 10 checks passed
@MikeNeilson MikeNeilson deleted the devops/update-logging-to-new-standard branch November 4, 2025 18:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants