chore: expand JSDoc for regex pattern fields and clarify EvalRun field descriptions - #49
Open
fern-api[bot] wants to merge 4 commits into
Open
chore: expand JSDoc for regex pattern fields and clarify EvalRun field descriptions#49fern-api[bot] wants to merge 4 commits into
fern-api[bot] wants to merge 4 commits into
Conversation
fern-api
Bot
force-pushed
the
fern-bot/2026-09-10_21-49-32_753
branch
2 times, most recently
from
September 10, 2026 23:04
dba93cf to
db50444
Compare
fern-api
Bot
force-pushed
the
fern-bot/2026-09-10_21-49-32_753
branch
from
September 10, 2026 23:11
db50444 to
e82cb5c
Compare
Generated by Fern CLI Version: unknown Generators: - fernapi/fern-typescript-sdk: 3.63.0
…larify EvalRun field descriptions Update documentation comments across `StructuredOutput`, `CreateStructuredOutputDto`, `UpdateStructuredOutputDto`, and `EvalRun` to provide clearer guidance for SDK consumers. Key changes: - Add detailed JSDoc to `regexPattern` fields explaining how simulation evaluations build their canonical transcript (User/AI dialogue, tool calls, tool results) and how this differs from production-call and call-preview extraction - Clarify `EvalRun.results` description to reflect individual Eval semantics rather than suite-level semantics - Simplify `EvalRun.cost` and `EvalRun.costs` descriptions for conciseness 🌿 Generated with Fern
…d descriptions Update documentation comments across `StructuredOutput`, `CreateStructuredOutputDto`, `UpdateStructuredOutputDto`, and `EvalRun` to provide clearer guidance for SDK consumers. Key changes: - Add detailed JSDoc to `regexPattern` fields explaining how simulation evaluations build their canonical transcript (User/AI dialogue, tool calls, tool results) and how this differs from production-call and call-preview extraction - Clarify `EvalRun.results` description to reflect individual Eval semantics rather than suite-level semantics - Simplify `EvalRun.cost` and `EvalRun.costs` descriptions for conciseness 🌿 Generated with Fern
fern-api
Bot
force-pushed
the
fern-bot/2026-09-10_21-49-32_753
branch
from
September 10, 2026 23:47
e82cb5c to
f21c240
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
2.0.1 → 2.0.2
Update documentation comments across
StructuredOutput,CreateStructuredOutputDto,UpdateStructuredOutputDto, andEvalRunto provide clearer guidance for SDK consumers.Key changes:
regexPatternfields explaining how simulation evaluationsbuild their canonical transcript (User/AI dialogue, tool calls, tool results) and
how this differs from production-call and call-preview extraction
EvalRun.resultsdescription to reflect individual Eval semantics ratherthan suite-level semantics
EvalRun.costandEvalRun.costsdescriptions for conciseness🌿 Generated with Fern