feat: add customFields for CustomerResponseStruct #50
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cyl3x
approved these changes
Dec 26, 2025
FlorianKe
approved these changes
Jan 5, 2026
mstegmeyer
approved these changes
Jan 5, 2026
untilu29
deleted the
feat/add-custom-feild-for-customer-response-struct
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Why is this change necessary?
The
CustomerResponseStructwas missing a customFields property to support custom data storage for customer responses in app integrations2. What does this change do, exactly?
Adds a
customFieldsproperty (array<string, mixed>) to CustomerResponseStruct with a default empty array value. This allows app developers to include custom field data when responding with customer information through the App SDK3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist