Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More convenient dria serve #20

Open
erhant opened this issue Feb 26, 2024 · 0 comments
Open

More convenient dria serve #20

erhant opened this issue Feb 26, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@erhant
Copy link
Member

erhant commented Feb 26, 2024

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

@erhant erhant added the enhancement New feature or request label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant