chore(deps): bump @styx-api/core to 0.6.0 - #13
Merged
Conversation
Picks up nested-struct `_params` factories and snake_case kwargs in the generated Python snippets (styx-ts#48). Python results tab now renders nested structs / union variants as factory calls (`tool_x_params(...)`) instead of raw tagged dicts; TypeScript snippets are unchanged. No hub code changes needed - the snippet flows straight from `renderPythonCall` in @styx-api/core.
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.
Bumps
@styx-api/core0.5.0->0.6.0(styx-ts#48, published to npm).Effect
The Python results tab now renders nested structs / union variants as factory calls - e.g.
ants.tool_corrected_output_params(corrected_output_file_name="...")- instead of raw tagged dicts{"@type": ...}. Root kwargs with camelCase wire ids also become snake_case. TypeScript snippets are unchanged.No hub code changes
The snippet flows straight from
renderPythonCallin@styx-api/core(worker.ts) with zero hub-side snippet logic, so only the pin + lockfile move. The build-time__STYX_CORE_VERSION__lockstep check resolves to the new version on rebuild.Validated locally
npm ci(clean, no lock churn),npm run check(0 errors),npm run test(206 pass),npm run build(success) - all against the pinned 0.6.0.