Skip to content

[Kotlin] Update to Definitely Non-Null Types Where Appropriate #496

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

Merged
merged 26 commits into from
Jun 27, 2022

Conversation

jeffgbutler
Copy link
Member

Update the Kotlin DSL to use Kotlin 1.7's new "definitely non-null" types where appropriate. This helps us to more accurately represent the nullable/non-nullable expectations for API method calls.

@jeffgbutler jeffgbutler added this to the 1.4.1 milestone Jun 27, 2022
@jeffgbutler jeffgbutler merged commit f0c1d5a into mybatis:master Jun 27, 2022
@jeffgbutler jeffgbutler deleted the definitely-non-null branch June 27, 2022 21:20
@coveralls
Copy link

coveralls commented Jun 27, 2022

Coverage Status

Coverage remained the same at 100.0% when pulling ec771bd on jeffgbutler:definitely-non-null into 453c2b7 on mybatis:master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants