Add null check for paginator hasNextPage

[davidh44]

Motivation and Context

Add null check for paginator hasNextPage()

Modifications

Previous

        @Override
        public boolean hasNextPage(ListAliasesResponse previousPage) {
            return previousPage.truncated().booleanValue();
        }

Updated

        @Override
        public boolean hasNextPage(ListAliasesResponse previousPage) {
            return previousPage.truncated() != null && previousPage.truncated().booleanValue();
        }

Testing

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[joviegas]

1. Can we please write a codegen test with expected java class and codegen class?
2. Also in what cases do we get this as Null ? Can we write a test case for the same

[davidh44]

Added tests
The service will always populate the field, but customer unit tests may not populate the more_results field in the response because it previously did not exist

[sonarqubecloud]

Quality Gate failed

Failed conditions
33.3% Coverage on New Code (required ≥ 80%)
4.4% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud