Skip to content
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

fix: use correct nullable types when referencing named mappings #1237

Merged
merged 1 commit into from Apr 15, 2024

Conversation

latonz
Copy link
Contributor

@latonz latonz commented Apr 13, 2024

Closes #1236

@latonz latonz self-assigned this Apr 13, 2024
@latonz latonz enabled auto-merge (squash) April 13, 2024 02:38
@latonz latonz requested a review from ni507 April 13, 2024 02:38
@latonz latonz force-pushed the 1236-named-mappings-nullables branch from 9685d7d to ba10f42 Compare April 14, 2024 22:32
@latonz latonz merged commit b3f79e8 into riok:main Apr 15, 2024
17 checks passed
@latonz latonz deleted the 1236-named-mappings-nullables branch April 15, 2024 06:47
Copy link

🎉 This PR is included in version 3.5.1-next.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

🎉 This PR is included in version 3.5.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

feat: forward null values into the mapping function (if supported) when specified on property level
2 participants