-
Notifications
You must be signed in to change notification settings - Fork 180
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
add collectionSettersMode none #467
Comments
Good suggestion @kronic Would be great if you could tackle this and create a PR 🙏🏻 The implementation in the example above is probably not thread safe. Perhaps we could leverage private Lazy<Collection<SomeClass>> _someProp = new Lazy<Collection<SomeClass>>();
public Collection<SomeClass> SomeProp
{
get
{
return _someProp.Value;
}
} |
@mganss |
@kronic I think the For example We'd need to make sure only sane combinations can be chosen, e.g. a private setter or no setter would require an initialization other than |
--collectionSettersMode=none
The text was updated successfully, but these errors were encountered: