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

feat: fix incorrect private set when ~MemberVisibility.Accessible is used #933

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

TimothyMakkison
Copy link
Collaborator

@TimothyMakkison TimothyMakkison commented Nov 20, 2023

feat: fix incorrect private set when ~MemberVisibility.Accessible is used

Description

Prevents the invalid generation of set to a private set property if ~MemberVisibility.Accessible is used.

Fixes #932

Checklist

  • The existing code style is followed
  • The commit message follows our guidelines
  • Performed a self-review of my code
  • The documentation is updated (as applicable)
  • Unit tests are added/updated

Copy link

codecov bot commented Nov 20, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (86408ce) 91.49% compared to head (bae8838) 91.50%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #933      +/-   ##
==========================================
+ Coverage   91.49%   91.50%   +0.01%     
==========================================
  Files         215      215              
  Lines        7217     7216       -1     
  Branches      873      873              
==========================================
  Hits         6603     6603              
+ Misses        408      407       -1     
  Partials      206      206              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@latonz latonz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this fast bugfix 😊

test/Riok.Mapperly.Tests/Mapping/UnsafeAccessorTest.cs Outdated Show resolved Hide resolved
@latonz latonz merged commit b60441a into riok:main Nov 21, 2023
19 checks passed
@mentallabyrinth
Copy link

Thank you for the fast fix! Do you have an ETA on when the next release will be available in nuget?

Copy link

🎉 This PR is included in version 3.3.0-next.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@latonz
Copy link
Contributor

latonz commented Nov 22, 2023

A preview release including this bug fix is published. We don't have an ETA on the next stable release, probably in a couple weeks.

@mentallabyrinth
Copy link

Thank you very much!

@TimothyMakkison TimothyMakkison deleted the private_set branch November 22, 2023 13:33
Copy link

🎉 This PR is included in version 3.3.0 🎉

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Non-public scope property getter/setter, private member mapping ignored.
3 participants