You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6038ee2
Browse filesBrowse the repository at this point in the historyBrowse files
authored
feat!: Add pagination support to ListTaskPushNotificationConfig with Result wrapper (#552)
# Description
Implements pagination support for push notification config listing by
introducing
ListTaskPushNotificationConfigResult record, following the same pattern
as
ListTasksResult. This allows the API to return both the list of configs
and a
nextPageToken for pagination.
Changes:
- Created ListTaskPushNotificationConfigResult record with configs list
and nextPageToken
- Updated ListTaskPushNotificationConfigResponse to use Result type
- Updated all server handlers to return Result wrapper
- Updated ProtoUtils mappers for Result conversion
- Updated all transport implementations (REST, gRPC, JSONRPC) on both
client and server
- Updated client interface and implementations
- Fixed test to use Result type
Updated all PushNotificationConfigStore implementations and tests to use
the new
ListTaskPushNotificationConfigParams/ListTaskPushNotificationConfigResult
API
instead of the old String-based getInfo method.
Changes to implementations:
- InMemoryPushNotificationConfigStore: Fixed bug where pageSize - 1 was
used
instead of pageSize, causing one less item to be returned than requested
- JpaDatabasePushNotificationConfigStore: Implemented pagination logic
matching
the in-memory implementation
- Added helper methods for pagination: findFirstIndex,
convertPushNotificationConfig
- Updated all test files with getInfoAsList helper method to maintain
compatibility
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make
sure it goes smoothly:
- [X] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md).
- [X] Make your Pull Request title in the
<https://www.conventionalcommits.org/> specification.
- Important Prefixes for
[release-please](https://github.com/googleapis/release-please):
- `fix:` which represents bug fixes, and correlates to a
[SemVer](https://semver.org/) patch.
- `feat:` represents a new feature, and correlates to a SemVer minor.
- `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking
change (indicated by the `!`) and will result in a SemVer major.
- [X] Ensure the tests pass
- [X] Appropriate READMEs were updated (if necessary)
Fixes#535 🦕
---------
Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
Co-authored-by: Kabir Khan <kkhan@redhat.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copy file name to clipboardExpand all lines: extras/push-notification-config-store-database-jpa/src/main/java/io/a2a/extras/pushnotificationconfigstore/database/jpa/JpaDatabasePushNotificationConfigStore.java
0 commit comments