feat(runner): align top-level input schema with inner (initPreset enum + drop preAuthenticate section caption) - #15
Merged
Conversation
…m + drop preAuthenticate section caption) Follow-up to #12. That PR copied the preAuthenticate property block from the inner schema but left two other top-level / inner drifts unaddressed: 1. preAuthenticate had `sectionCaption: "Authentication"` which forces a separate section header in the Console form. The maintainer asked to keep the field inline with the others — dropping the section caption. 2. The initPreset enum on the top-level schema still has only 4 values (none, mcp_native, cli_native, mcpc) — the inner schema added 4 more in PR #6 (api_native, mcp_only, cli_only, api_only) plus a rewritten description distinguishing _native vs _only semantics and matching enumTitles. The Console preset dropdown was missing the 4 new options. This PR copies both fields (initPreset.description, initPreset.enum, initPreset.enumTitles) from the inner schema verbatim and removes the sectionCaption from preAuthenticate. Together with #12 this brings the top-level schema in line with the inner copy for the two fields users actually interact with in the Console. Out of scope: the full inner→top-level merge + inner deletion (that's #13, still in review). Once #13 lands this PR's changes become redundant but harmless. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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.
Summary
Two-line follow-up to #12 that closes the remaining top-level / inner schema drift visible in the Apify Console form:
preAuthenticate.sectionCaption: "Authentication"— the Console was rendering preAuthenticate under its own collapsible section header rather than inline with the other fields. Maintainer asked to keep it inline.initPreset.enumfrom 4 → 8 values + adds matchingenumTitles+ rewritesdescription— the surface-aware presets shipped in Surface-aware preset overhaul: api_native, *_only variants, enhancednone#6 (api_native,mcp_only,cli_only,api_only) were live in the inneractors/runner/.actor/input_schema.jsonbut not in the canonical top-level.actor/input_schema.json. The Console preset dropdown showed only 4 options.Both fields were copied verbatim from
actors/runner/.actor/input_schema.jsonon current main.Why
Same pattern as #12 — drift between the two
.actor/directories means Console form changes silently lag the inner schema's progress. #13 (full consolidation + inner deletion) will fix this comprehensively, but in the meantime users of the deployed Actor need the dropdowns and field layout to match what the runner code actually supports.Diff scope
Single file:
.actor/input_schema.json. ~10-15 lines changed in two adjacent blocks. No code changes, no other files touched.Test plan
jq . .actor/input_schema.jsonexits 0.Relationship to #13
#13 (
refactor(runner): consolidate to a single Actor) already includes both these changes as part of the full inner→top-level merge. If #13 lands first, this PR becomes a no-op auto-resolve during rebase. If this PR lands first, #13 still applies cleanly (same final state).🤖 Generated with Claude Code