Skip to content

Strategy should use existing value even when setter is available #145

@roryprimrose

Description

@roryprimrose

The scenario here is when a property has a setter but also already has a value assigned. That value should just be populated rather than generated. The main reason is because the type of the instance could be more specific than the type that the property defines.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions