Conversation
David Elner (delner)
requested review from
Abhijeet Prasad (AbhiPrasad) and
Andrew Kent (realark)
David Elner (delner)
added
the
documentation
Joshua Wootonn (joshuawootonn)
left a comment
Joshua Wootonn (joshuawootonn)
left a comment
There was a problem hiding this comment.
Thank you for doing this. It's very needed!
|
|
||
| | Field | Type | Description | | ||
| |-------|------|-------------| | ||
| | `type` | `string` | Always `"braintrust.staticParameters"` for inline (code-defined) parameters | |
There was a problem hiding this comment.
Do you think we should also mention braintrust.parameters, or is that out of scope?
There was a problem hiding this comment.
Could you explain what braintrust.parameters is? Not sure how that overlaps (or doesn't.)
There was a problem hiding this comment.
Sorry I somehow missed the notifications for these comments.
braintrust.parameters and braintrust.staticParameters are the DTOs for how the remote eval server communicates with the playground.
braintrust.parameters signals that the user created some Parameters and is loading them here for this remote eval server. (ref)
braintrust.staticParameters signals that the user has defined a schema inline on the Eval
The playground uses this information to conditionally render things like the Version selector for selecting different versions of your Parameters to use in the playground.
David Elner (delner)
force-pushed
the
feature/remote-evals-params
branch
from
1b34891 to
4420067
Compare
|
LGTM! I'll try this out with a coding agent when I implement in java |
|
David Elner (@delner) Joshua Wootonn (@joshuawootonn) -- I used this to implement params in the java SDK. Can we get this merged? |
3 participants
This pull request adds a spec for remote eval parameters under
features/remote-evals/params.