Release v1.0.0 #2

Merged
Rene Nochebuena merged 11 commits from release/v1.0.0 into main 2025-04-10 18:30:35 -06:00
No description provided.
Rene Nochebuena added 11 commits 2025-04-10 18:15:30 -06:00
Add a structured logging utility with custom prefixes and suffixes
Some checks failed
Go CI/CD / go-ci (push) Has been cancelled
94c6e882fb
Introduce a logging system supporting multiple severity levels, JSON formatting, and customizable prefixes and suffixes inspired by Dr. Stone. Includes random success and failure quotes to make logging more dynamic and engaging.
Refactor getRandomPrefix to simplify StoneLevel mapping.
All checks were successful
Go CI/CD / go-ci (push) Successful in 10m4s
4046c447cc
Replaced the switch-case with a map for StoneLevel to prefix mapping. This reduces redundancy, improves readability, and maintains default handling for unsupported levels. Functionality remains unchanged.
Set SonarQube to wait for quality gate results.
All checks were successful
Go CI/CD / go-ci (push) Successful in 10m8s
8fad79b823
Added `sonar.qualitygate.wait=true` to enforce the build process waits for SonarQube's quality gate results. This ensures code quality checks are completed before proceeding.
Add tests for log level string and color representations
Some checks failed
Go CI/CD / go-ci (push) Failing after 6m59s
4557b8050c
Introduce unit tests to verify the string and color outputs of StoneLevel. These tests ensure the correct mapping of log levels to their respective string values and color codes.
Add paths for Go test and coverage reports in Sonar config
Some checks failed
Go CI/CD / go-ci (push) Failing after 6m52s
b66a17197e
This update includes `test-report.out` and `coverage.out` for improved test and coverage integration with SonarQube analysis. It ensures better reporting and alignment with project quality standards.
Validate log level and improve test coverage
Some checks failed
Go CI/CD / go-ci (push) Has been cancelled
00e6488185
Added validation to ensure log levels are within valid bounds in `SetLogLevel`. Simplified prefix mapping logic by removing the fallback to INFO level. Expanded test coverage with new test cases for plain text and JSON log outputs.
Add test for muted plaintext log behavior
Some checks failed
Go CI/CD / go-ci (push) Has been cancelled
e84f7bd810
This test verifies that logs below the ERROR level are properly muted when plaintext logging is enabled without JSON formatting. It ensures that log output adheres to the configured log level settings.
Add tests for handling invalid log levels in SetLogLevel
All checks were successful
Go CI/CD / go-ci (push) Successful in 10m4s
b7202bc141
Ensure that setting an invalid log level with SetLogLevel does not affect existing log behavior. Additional test cases verify that only appropriate log messages are displayed based on the current log level.
Add tests for panic and fatal log handling
Some checks failed
Go CI/CD / go-ci (push) Has been cancelled
d126d4ef7a
Introduce tests for handling panic and fatal log scenarios, including recovery from panics and execution of external processes to test fatal behavior. Adjusted logging levels and prefixes to ensure consistency for PANIC logs.
Refactor test binary location and update sonar exclusions
All checks were successful
Go CI/CD / go-ci (pull_request) Successful in 10m12s
Go CI/CD / go-ci (push) Successful in 10m8s
a7c6a85084
Moved the test binary from "tests" to "testbin" for better organization. Updated `sonar-project.properties` to exclude the new directory from analysis and adjusted test references accordingly.
Merge pull request 'Log System Implementation' (#1) from feature/log-system-implementation into develop
All checks were successful
Go CI/CD / go-ci (push) Successful in 10m5s
Go CI/CD / go-ci (pull_request) Successful in 10m6s
6df531d73b
Reviewed-on: #1
Reviewed-by: Cloud Administrator <cloud-admin@noreply.gitstormr.dev>
Cloud Administrator approved these changes 2025-04-10 18:30:19 -06:00
Rene Nochebuena merged commit 14687cfc2f into main 2025-04-10 18:30:35 -06:00
Rene Nochebuena referenced this issue from a commit 2025-04-10 18:30:36 -06:00
Sign in to join this conversation.
No description provided.