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
On branch edburns/dd-2824425-fix-record-vs-getter-discrepancy
modified: .github/copilot-instructions.md
modified: README.md
modified: src/site/markdown/advanced.md
modified: src/site/markdown/cookbook/error-handling.md
modified: src/site/markdown/cookbook/managing-local-files.md
modified: src/site/markdown/cookbook/multiple-sessions.md
modified: src/site/markdown/cookbook/persisting-sessions.md
modified: src/site/markdown/cookbook/pr-visualization.md
modified: src/site/markdown/documentation.md
modified: src/site/markdown/getting-started.md
modified: src/site/markdown/hooks.md
modified: src/site/markdown/index.md
modified: src/site/markdown/mcp.md
When the accessor style changed
Commit f5e9662 — February 10, 2026, authored by Bruno Borges.
"Refactor data access methods in tests to use new naming conventions"
Updated test assertions … to reflect changes in data access methods from getX() to x().
This was a massive breaking change across all 40+ event data types in com.github.copilot.sdk.events. Every public static class FooData with JavaBean getters/setters was converted to a public record FooData(...). This removed all getX() / setX() methods and replaced them with record component accessors (x()).
The commit was merged via PR #117 (feat/records-for-data-types) and shipped in v1.0.9 (the first release tag that contains it, alongside v1.0.10 and v1.0.11).
Timeline summary:
Before f5e9662: AssistantMessageData was a mutable static class with getContent(), setContent(), etc.
After f5e9662 (v1.0.9+): all event data types became Java records — content(), currentTokens(), tokenLimit(), messagesLength(), etc.
The README's Quick Start code was never updated to match — it still showed getContent() / getCurrentTokens() etc. until the fix applied in our current session.
0 commit comments