abra recipe fetch can only fetch a single recipe #530

Closed
opened 2023-11-05 19:53:54 +00:00 by wykwit · 1 comment
Member

description

The behaviour of recipe fetch command has changed in commit 0be532692d (with coop-cloud/abra#353) without changing the description to fit. The command can only fetch a single recipe, it doesn't retrieve all recipes anymore.

Current help message:

$ ./abra recipe help fetch
NAME:
   abra recipe fetch - Fetch recipe(s)

USAGE:
   abra recipe fetch [command options] [<recipe>]

DESCRIPTION:
   Retrieves all recipes if no <recipe> argument is passed

OPTIONS:
   --debug, -d     Show DEBUG messages
   --no-input, -n  Toggle non-interactive mode

steps to reproduce

  • execute abra recipe fetch without specifying a recipe

expected result

Per help message the expected result is to fetch all recipes similar to behaviour of abra catalogue generate. However, since the catalogue subcommand seems to cover that use-case well enough already, I would expect this subcommand to require specifying a recipe and displaying help message whenever it is not specified.

actual result

$ abra recipe fetch
FATA[0000] unable to open /home/user/.abra/recipes: repository does not exist

comments

The recipe subcommand should stay simple and deal with single recipes only.

The catalogue still seems to evolve and as more changes are made in the code around it, it would be beneficial to keep catalogue and recipe subcommands untangled. I would suggest to leave dealing with (multiple) repositories within the catalogue subcommand's duties and perhaps split off more subsubcommands from there later. This command then would require specifying recipes, and so the description would have to be updated accordingly.

## description The behaviour of `recipe fetch` command has changed in commit 0be532692d (with coop-cloud/abra#353) without changing the description to fit. The command can only fetch a single recipe, it doesn't retrieve all recipes anymore. Current help message: ``` $ ./abra recipe help fetch NAME: abra recipe fetch - Fetch recipe(s) USAGE: abra recipe fetch [command options] [<recipe>] DESCRIPTION: Retrieves all recipes if no <recipe> argument is passed OPTIONS: --debug, -d Show DEBUG messages --no-input, -n Toggle non-interactive mode ``` ## steps to reproduce - execute `abra recipe fetch` without specifying a recipe ### expected result Per help message the expected result is to fetch all recipes similar to behaviour of `abra catalogue generate`. However, since the `catalogue` subcommand seems to cover that use-case well enough already, I would expect this subcommand to require specifying a recipe and displaying help message whenever it is not specified. ### actual result ``` $ abra recipe fetch FATA[0000] unable to open /home/user/.abra/recipes: repository does not exist ``` ## comments The `recipe` subcommand should stay simple and deal with single recipes only. The catalogue still seems to evolve and as more changes are made in the code around it, it would be beneficial to keep `catalogue` and `recipe` subcommands untangled. I would suggest to leave dealing with (multiple) repositories within the `catalogue` subcommand's duties and perhaps split off more subsubcommands from there later. This command then would require specifying recipes, and so the description would have to be updated accordingly.
wykwit added the
bug
label 2023-11-05 19:53:54 +00:00
Owner

My boiling hot take!

image

Let's get the functionality back, I think it was a bug from me in the arg handling...

A test wasn't written 🙃 one would be good...

My boiling hot take! ![image](/attachments/f80b2bd8-ba6f-44e7-85d1-ef9018b1dac6) Let's get the functionality back, I think it was a bug from me in the arg handling... A test wasn't written 🙃 one would be good...
p4u1 closed this issue 2024-01-24 15:01:34 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#530
No description provided.