Skip to content

Conversation

@shaljam
Copy link
Contributor

@shaljam shaljam commented Oct 2, 2025

Submit a pull request

CLA

  • I have signed the Stream CLA (required).
  • The code changes follow best practices
  • Code changes are tested (add some information if not applicable)

Description of the pull request

It is possible to get the fields on request objects. Also fixed getter methods missing in the javadoc.

@shaljam shaljam force-pushed the getter-hashcode-request branch 3 times, most recently from 1a3bfb6 to e44dc6d Compare October 2, 2025 14:42
@shaljam shaljam force-pushed the getter-hashcode-request branch from e44dc6d to 83ae1a0 Compare October 8, 2025 09:02
@shaljam shaljam marked this pull request as ready for review October 8, 2025 09:09
@shaljam shaljam merged commit 242fbc6 into main Oct 15, 2025
1 check passed
@shaljam shaljam deleted the getter-hashcode-request branch October 15, 2025 15:23
adityaalifn added a commit that referenced this pull request Oct 22, 2025
…ization

The ObjectMapper configuration added in PR #205 set PropertyAccessor.GETTER
visibility to NONE, which disabled ALL getter methods including those
annotated with @JsonAnyGetter. This broke serialization of additionalFields
in channels and messages, causing custom object fields to appear as empty.

Changed to use field-based serialization while still respecting explicit
Jackson annotations (@JsonAnyGetter, @JsonProperty, etc):
- Set PropertyAccessor.ALL to NONE (disable auto-detection)
- Set PropertyAccessor.FIELD to ANY (use field-based serialization)

This preserves the intent of PR #205 (avoiding getter auto-detection)
while fixing additionalFields serialization.

Fixes: #205
adityaalifn added a commit that referenced this pull request Oct 22, 2025
…ization (#209)

The ObjectMapper configuration added in PR #205 set PropertyAccessor.GETTER
visibility to NONE, which disabled ALL getter methods including those
annotated with @JsonAnyGetter. This broke serialization of additionalFields
in channels and messages, causing custom object fields to appear as empty.

Changed to use field-based serialization while still respecting explicit
Jackson annotations (@JsonAnyGetter, @JsonProperty, etc):
- Set PropertyAccessor.ALL to NONE (disable auto-detection)
- Set PropertyAccessor.FIELD to ANY (use field-based serialization)

This preserves the intent of PR #205 (avoiding getter auto-detection)
while fixing additionalFields serialization.

Fixes: #205
@github-actions github-actions bot mentioned this pull request Oct 22, 2025
adityaalifn added a commit that referenced this pull request Oct 22, 2025
…ization

The ObjectMapper configuration added in PR #205 set PropertyAccessor.GETTER
visibility to NONE, which disabled ALL getter methods including those
annotated with @JsonAnyGetter. This broke serialization of additionalFields
in channels and messages, causing custom object fields to appear as empty.

Changed to use field-based serialization while still respecting explicit
Jackson annotations (@JsonAnyGetter, @JsonProperty, etc):
- Set PropertyAccessor.ALL to NONE (disable auto-detection)
- Set PropertyAccessor.FIELD to ANY (use field-based serialization)

This preserves the intent of PR #205 (avoiding getter auto-detection)
while fixing additionalFields serialization.

Fixes: #205
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants