Skip to content

Add test asserting that feature toggling results in observable behavior change #3154

Description

@jaschdoc

The test should observe that when a processor has not yet opted into enableNewFeatures, the KSPropertyDeclaration.backingField property returns null for a property declaration that has a backing field. Then it should opt in to enableNewFeatures and assert that the backingField property is the expected backing field.
The same should happen for all other change points, i.e., Resolver.getSymbolsWithAnnotation, KSPropertyDeclaration.annotations, and KSBackingField.modifiers.

Activity

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

Metadata

Metadata

Assignees

Labels

P1major features or blocking bugscoreIssues related to the core implementation of KSP API.

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions