Skip to content

Add a confirm for "dangerous" commands #129

@jwikman

Description

@jwikman

Hi,

I just, by mistake, managed to execute "ALTB: Renumber AL Objects" in a project that had 30+ changed, but not yet committed, files.

When I noticed the mistake, I tried to hit all cancel buttons that was shown, but the complete renumber and save files actions was executed anyway. Resulting in 400+ modified files... Now I have to go through all files to make sure that I do not discard any important change.

Please, add a confirm on actions that potentially modifies a lot of files.

There could be other safeguards as well, like not permitting this kind of actions if there are uncommitted changed. But a confirm is much easier to implement and is probably "good enough".

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