Skip to content

Setting an optional field doesn't prompt for user input during "op plugin init" phase #280

@arunsathiya

Description

@arunsathiya

op CLI version

2.19.0-beta.01

Goal or desired behavior

The prompt should appear and it should be up to the user to set a value to it or not.

Current behavior

When a field is marked as optional, op plugin init phase completely skips user prompt for input for that field. In the example image below, I was expecting a "Username" field but the init phase skipped it and moved on to the second field, "Password":

image

I don't remember this being the case in the past. So, it might be a recent regression? 🤔

Relevant log output

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingop-cliFunctionality to be implemented in 1Password CLI. Needs to be done by 1Password Developers.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions