Skip to content

Agent corrective actions may not be optimal and lack validation #1705

Description

@mikadumont

Description

Direct customer feedback:

During a .NET upgrade, the agent detected missing constants between v1 and v2 of a package and recreated them in a new file. The customer didn't have time to determine whether that was the best corrective action.

Expected Behavior:

When the agent takes corrective action for breaking changes between package versions, it should explain its reasoning and flag the change for review rather than silently applying a fix that may not be idiomatic.

Activity

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions