Skip to content

More convenient dria serve #20

@erhant

Description

@erhant

When we type dria list, we see results like:

<contract-1> (last-modified)
<contract-2> (last-modified)
...

and we need to provide the entire <contract-id> to the serve options and such. We could perhaps use a more convenient option such as:

[1] <contract-1> (last-modified)
[2] <contract-2> (last-modified)
...

and then providing dria serve <contract-1> should be the same as dria serve 1.


Alternatively, we could have the serve argument coerce to the nearest similar knowledge, e.g. if we have test-knowledge and we type dria serve te that te should be inferred as test-knowledge

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions