Skip to content

docs(apify-actor-development): require explicit .inputSchema reference in actor.json (auto-discovery deprecated) #66

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.

Sign up for GitHub

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

Draft
DaveHanns wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs(apify-actor-development): require explicit .inputSchema reference in actor.json (auto-discovery deprecated) #66

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions skills/apify-actor-development/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -238,6 +238,8 @@ See [references/actor-json.md](references/actor-json.md) for complete actor.json

See [references/input-schema.md](references/input-schema.md) for input schema structure and examples.

When you create an input schema file, reference it explicitly from `.actor/actor.json` — either inline (`"inputSchema": { "type": "object", ... }`) or by path (`"inputSchema": "./input_schema.json"`, relative to `.actor/`). Do not rely on auto-discovery of `.actor/INPUT_SCHEMA.json` or root `INPUT_SCHEMA.json`; that fallback is deprecated per the input-schema specification and may be removed in a future platform release. The deprecated `.input` field is still recognized for backwards compatibility but should not be used in new Actors.

## Output schema

See [references/output-schema.md](references/output-schema.md) for output schema structure, examples, and template variables.
Expand Down
Loading