I'd particularly appreciate folks bringing their best edge cases (except Lann, his edge cases are too good). Thanks!

Weird issue where spin up --bindle spin-headers-env-routes-test/1.0.0 --bindle-server http://127.0.0.1:35339/v1/ works but spin up --bindle spin-headers-env-routes-test/1.0.0 --bindle-server http://127.0.0.1:35339/v1/ --listen 127.0.0.1:39453 says you can't use --bindle with the positional arg. Investigating.

Seems to happen when a trigger option is specified alongside a conflicty (source) flag.

If I remove the conflict I can see what's going on and CLAP IS INTERPRETING THE TRIGGER OPTION AS THE APP SOURCE AAAHH

So the issue is that we already have the positional trigger_args collection, which picks up all arguments not matched by up arguments. But now we have a positional arg for the app source, which picks up the first positional arg. But that means that if the app source is omitted, and there are trigger args being interpreted positionally, the first trigger arg gets interpreted as the app source (because it's in the first positional, er, position).

I am... actually not sure how to get around this.

At the moment the closest thing to a solution I can think of to this is to retain -f but allow it to take directories and registry references as well as plain files.

Lann notes that we could pretend -f stood for --from if that helps sell anybody on the above proposition.

Lann notes that we could pretend -f stood for --from if that helps sell anybody on the above proposition.

Commence massive disinformation campaign. In all seriousness though I like this solution.

#1179 presents an alternative proposal that is not as beautiful but might be more workable.

I think we are closing this in favour of #1179.