Option callback always fires even when it is not specified in the command invocation

[Andreas3333]

From the click docs:

Missing parameters:
If a parameter is not defined on the command line, the callback will still fire. This is different from how it works in optparse where
undefined values do not fire the callback. Missing parameters fire their callbacks at the very end which makes it possible for
them to default to values from a parameter that came before.

I am finding the first part of this statement, " If a parameter is not defined on the command line, the callback will still fire." to be true. However, "Missing parameters fire their callbacks at the very end..." I have not observed to be the case while experimenting.

Basically I am looking for a way to have options with callbacks not fire for them to be optional.

For example:

def cat_current_config(ctx, param, value):
    print("do cat")

def open_config_file(ctx, param, value):
    print("do edit")

@cli.command()
@click.option(
    "-c",
    "--cat",
    is_flag=True,
    callback=cat_current_config,
    is_eager=False,
    required=False
)
@click.option(
    "-e",
    "--edit",
    is_flag=True,
    callback=open_config_file,
    is_eager=True
)
@click.argument("foo", required=True)
def config(cat: Optional[str], edit: bool, foo: str) -> None:
    """List and edit settings.
    """
    print("---- Doing foo ----")
    print(foo)
    print(edit)
    print(cat)

Invoking:

tool config foo

Results as:

do edit
do cat
---- Doing foo ----
foo
None
None

I have experimented with setting a few different parameters on the command option cat, but have been unable to configure it's callback to not run if the option is not specified. Is it possible to do this in click?

Looking for input on this or If I am missing something entirely.