Replaced the ResultInfo class with a Java record for conciseness and immutability. Adjusted related validation logic and method calls to align with the new record structure. Minor updates to Javadoc documentation were also included.
Refined the condition for exception handling based on 'emptyResultThrowsException' to clarify when exceptions are triggered versus returning empty results. Updated Javadoc output files to reflect the latest documentation changes.
Introduced `ResponseValidatorTest` to comprehensively test the `ResponseValidator` class. Enhanced the project dependencies by updating JUnit to 5.12.2 and integrating Mockito with `mockito-junit-jupiter` 5.17.0 for mocking support. Clarified Javadoc for handling `RecordMultipleResponse` cases in `ResponseValidator`.
Introduced a new ResponseValidator class to encapsulate response validation logic, improving code readability and maintainability. Updated CfDnsClient to delegate response validation to this new class. Adjusted tests to align with the refactor and ensure proper exception handling.
Refactor record creation method to improve clarity
Renamed `recordCreate` to `recordCreateSld` to better align with its function of creating records specifically for SLDs. Updated relevant tests, documentation, and method references to use the new naming for consistency and improved readability
The Javadoc files have been regenerated to reflect updates in metadata including timestamps and headers. This ensures the documentation remains consistent with the latest source code revisions.
The Javadoc files have been regenerated to reflect updates in metadata including timestamps and headers. This ensures the documentation remains consistent with the latest source code revisions.
Renamed `recordCreate` to `recordCreateSld` to better align with its function of creating records specifically for SLDs. Updated relevant tests, documentation, and method references to use the new naming for consistency and improved readability.
Updated auto-generated Javadoc files to reflect changes for version 0.2.0-SNAPSHOT. This includes metadata, timestamps, and minor structural adjustments across multiple HTML files.
Updated the SonarQube project key in `pom.xml` to reflect the new naming convention. Simplified the CI script by removing redundant project key specification, ensuring consistency and maintainability.
Removed the hardcoded version of the Sonar Maven plugin to use the latest available version. This ensures compatibility with updates and reduces maintenance overhead.
Added `sonar.sourceEncoding` and updated Sonar Maven plugin to a specific version for improved compatibility. Adjusted SCM values to reflect the correct repository URLs under the `thischwa` namespace.
Replaced Sonar Scanner CLI with Maven Sonar plugin in the CI workflow for better integration and simplicity. Added SonarCloud configuration properties to `pom.xml` for centralized management. This streamlines the setup and ensures consistency across the project.
Updated the SonarCloud project identifier in README.md to reflect the correct project name. This ensures the badges display accurate data for the current project configuration.
Replaced outdated project directory, project key, and organization values with updated ones. This ensures proper integration with SonarQube and maintains accuracy in the pipeline configuration.
Removed the `sonar.sources` property as it is redundant in the current setup. SonarQube automatically detects source files, simplifying the configuration. This ensures the pipeline remains clean and easier to maintain.
Added the `-Dsonar.sources` property to specify the `src/main/java` directory for SonarQube analysis. This ensures the main Java source files are included in the scan, improving code quality assessment accuracy.
The test exclusions were overly broad and unnecessary as the tests are handled properly without them. This change simplifies the configuration while maintaining the intended functionality.
thischwa