-
Notifications
You must be signed in to change notification settings - Fork 435
Allow @JsonKey to be used on constructor parameters
#1505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I noticed that the current master branch has WIP commits, so I didn't update the CHANGELOG.md. |
|
@kevmoo Request for review |
|
@kevmoo I can run workflow successfully in my forked repo. |
|
failing tests? |
kevmoo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need changelog entries for both packages, too.
Co-authored-by: Kevin Moore <kevmoo@users.noreply.github.com>
|
@kevmoo
This dosen't seems to be caused by my commit. Should I modify |
Co-authored-by: Kevin Moore <kevmoo@users.noreply.github.com>
@kevmoo I need some help. We need to bump analyzer to 8.0.0 to pass the tests, but there are many version conflicts. Many packages have not yet adapted to analyzer 8.0.0. |
|
@kevmoo Plz take a look when you have a moment. |
| @@ -1,6 +1,7 @@ | |||
| ## 4.9.1-wip | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll do the follow-up here. We should bump this to 4.10 since we're adding a feature.
|
When will this go live on the pub? |
About #1437
Allow
@JsonKeyto be used on constructor parameters, where the@JsonKeyproperties will override the corresponding field properties.