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
args in roles.yaml #84
Comments
@sigoden Thanks, yes I did see that, still not understanding what significance the named params in the roles.yaml have. To be more specific, what is the difference (if any?) between the following 2 role definitions: - name: convert:json:yaml
prompt: convert __ARG1__ below to __ARG2__
- name: convert2:sdfgksjdfghksdfjghsdf:c434rhirfhs
prompt: convert __ARG1__ below to __ARG2__ It appears to me that both of these could be used as
? |
The The
|
Give role arg a meaningful name for convenience. |
Right, so that confirms what I was thinking—the names given in Would it make sense then to allow |
Without role arg, if you want to do following things:
You need to create three roles seperately
But with role arg, you only need to create one role:
It is a generic role now. |
If you want to use
|
✨amazing project btw!✨
I was trying to use the
translator:
role example, but I'm not quite understanding theARGn
substitutions and how they relate to the role name definition inroles.yaml
.Example roles.yaml:
Must I define the name as
translator:french
or can I make it generic and usetranslator:lang
? Or does it not matter? Isfrench
just a placeholder? Or is it a default? If it's a default, I would expect to be able to write:...without specifying a language parameter. But that doesn't work. You must type the full role spec. Am I using this incorrectly?
The text was updated successfully, but these errors were encountered: