abra app cmd ls <domain> #484

Closed
opened 2023-08-25 16:01:09 +00:00 by moritz · 3 comments
Member

If I want to execute some abra cmds I always have to look into the abra.sh or the README.
Something like abra app cmd ls <domain> that shows the available commands and some usage docs would make the life a bit easier.

If I want to execute some abra cmds I always have to look into the `abra.sh` or the `README`. Something like `abra app cmd ls <domain>` that shows the available commands and some usage docs would make the life a bit easier.
moritz added the
enhancement
label 2023-08-25 16:01:09 +00:00
decentral1se self-assigned this 2023-10-04 13:22:37 +00:00
Owner

@moritz would like to see this done. trying to think through it. I think some of the abra.sh examples I've checked are pretty chaotic and don't have a clear standard approach. So, parsing seems pretty scary. Maybe we could do a kind of recommended "docstring"? Any proposals?

@moritz would like to see this done. trying to think through it. I think some of the `abra.sh` examples I've checked are pretty chaotic and don't have a clear standard approach. So, parsing seems pretty scary. Maybe we could do a kind of recommended "docstring"? Any proposals?
decentral1se added this to the (deleted) project 2023-10-06 09:27:58 +00:00
Author
Member

A standardized docstring format would be perfect! As for now it could simply print all the bash function names. A way to differentiate between public and private/internal functions would be nice. I.e my_public_function(), _internal_function()

A standardized docstring format would be perfect! As for now it could simply print all the bash function names. A way to differentiate between public and private/internal functions would be nice. I.e `my_public_function()`, `_internal_function()`
decentral1se referenced this issue from a commit 2023-10-17 19:20:50 +00:00
Owner

With coop-cloud/abra#376 we have a simple listing now. If anyone wants to come up with a docstring format or otherwise work this out to be more informative, please open up another ticket.

With https://git.coopcloud.tech/coop-cloud/abra/pulls/376 we have a simple listing now. If anyone wants to come up with a docstring format or otherwise work this out to be more informative, please open up another ticket.
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#484
No description provided.