Uh oh!
There was an error while loading. Please reload this page.
feat(abg)!: replace data class perks by code generation in bindings - #1644
feat(abg)!: replace data class perks by code generation in bindings#1644Vampire wants to merge 1 commit into
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
fcb93fe to
f2e6c05Compare6e0c383 to
05942abComparef2e6c05 to
f9bff8aCompare26ff564 to
915be83Compare5b756f4 to
a485fe4Compare915be83 to
01e7a87Comparea485fe4 to
6c58c0dCompare01e7a87 to
781eb1bCompare6c58c0d to
66b9afdCompare781eb1b to
248813fCompare66b9afd to
f8e466fCompare248813f to
a5da3b1Comparef8e466f to
eb02b5aComparea5da3b1 to
f58ac6bCompareeb02b5a to
36a0a91Comparef58ac6b to
f11c738Compare36a0a91 to
8895541Comparef11c738 to
5e87ccbCompare8895541 to
4281b5dCompare5e87ccb to
c89a7e1CompareUh oh!
There was an error while loading. Please reload this page.
| - The `equals` method will work like before. | ||
| - The `hashCode` method will work like before. | ||
| - The `toString` method will work like before. | ||
| - Destructuring assignments are not possible anymore as this will likely break silently or during |
There was a problem hiding this comment.
I initially wanted to ask why this change is made under v2 of the bindings server, and it's probably because of this remark about destructuring. I think it's enough to provide component1...componentN functions, then destructuring should work, and we wouldn't have to bump the route version just yet.
There was a problem hiding this comment.
My plan is to revisit our discussion we had on Slack to ensure that there's no simpler option to achieve what we want. Sometimes ideas come after time 😄
There was a problem hiding this comment.
Let's see if someone has some interesting take on this: https://kotlinlang.slack.com/archives/C8C4JTXR7/p1729233924861659
There was a problem hiding this comment.
I think it's enough to provide component1...componentN functions, then destructuring should work, and we wouldn't have to bump the route version just yet.
It would not be, as said on Slack.
It was intentional I left them out.
And additionally the copy method now also enforces named-arguments which is also a breaking change.
So to replicate here too, the goal here was not to somehow make it compatible with the upcoming Kotlin versions, but to improve the API to the originally intended way.
That this also fixes the copy visibility thing is merely a by-product and just was the trigger to finally have a look at it.
4281b5d to
1f9acc7Comparec89a7e1 to
fb71bbbCompare9d293a1 to
30dd897Compareac57787 to
6a4b37cCompare30dd897 to
9d65dc9Compare6a4b37c to
e1c02e0Compare9d65dc9 to
cd64a8eComparee1c02e0 to
f416585Comparecd64a8e to
62d0334Comparef416585 to
38ae26eCompare62d0334 to
1692740Compare38ae26e to
78478e8Compare0d20faa to
361c817Compare2e625de to
792beb4Compare792beb4 to
6edeaacCompare29455da to
5ea294cCompare44c7839 to
a157006Compare5ea294c to
56f3508Comparea157006 to
ff4ec7aCompare56f3508 to
aa3ec98Compareff4ec7a to
63a6397Compareaa3ec98 to
0a56a01Compare
Fixes#1629