Skip to content

docs: ia v3 followups - Limits and dataset & kv store schemas#2747

Open
TC-MO wants to merge 2 commits into
masterfrom
ia-v3-followups
Open

docs: ia v3 followups - Limits and dataset & kv store schemas#2747
TC-MO wants to merge 2 commits into
masterfrom
ia-v3-followups

Conversation

@TC-MO

@TC-MO TC-MO commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Resolves issue 2476

Removes Limits from topnav to Account section
Moves dataset & kv store schema to Storage
Restructures Storage to account for new content
Restructures KV Store schema docs to align wiwth dataset schema doc structure
Updates links within OpenAPI spec

TC-MO added 2 commits July 7, 2026 20:55
…ype (#2746)

Move the dataset and key-value store schema pages out of Actor development
into the Storage section, grouped under Dataset and Key-value store
categories. Add nginx redirects for the old URLs and repoint internal
links; page slugs are unchanged.

Also align the two schema docs to a parallel structure and headings,
correct the Actor definition schema list to cover input and output
schemas, and drop first-person voice from the storage pages.
Move the Limits page from the top navigation into the Account section
(/limits -> /account/limits) and add an nginx redirect. Remove the
top-nav entry from the shared theme.
@TC-MO TC-MO self-assigned this Jul 7, 2026
@TC-MO TC-MO added documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team. labels Jul 7, 2026
@apify-service-account

apify-service-account commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

✅ Preview for this PR (commit ea9182a) is ready at https://pr-2747.preview.docs.apify.com (see action run).

@apify-service-account

Copy link
Copy Markdown
Contributor

Important

Action required@TC-MO please coordinate this docs PR with the Python API client PR linked below.

Because this PR modifies the OpenAPI specification, the generated models in apify-client-python must be regenerated to stay in sync. This has already been done automatically:

A companion PR has been opened in apify-client-python with the regenerated models: apify/apify-client-python#923

  • Please make sure to review and merge both PRs together to keep the OpenAPI spec and API clients in sync.
  • You can ask for review and help from the Tooling team if needed.

@TC-MO TC-MO requested a review from marcel-rbro July 8, 2026 08:07
@TC-MO TC-MO marked this pull request as ready for review July 8, 2026 08:07
@marcel-rbro

marcel-rbro commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Optional / out of strict scope — flagging since this PR already updates OpenAPI spec links and could be expanded to finish the set.

These four spec links still point at the old actor-definition/dataset-schema path. They're pre-existing and not broken by this PR — they resolved before and still resolve now (via the /platform-strip + new schema-move redirect, just an extra hop). If you'd like to knock them out here for consistency, swap /platform/actors/development/actor-definition/dataset-schema/storage/dataset-schema:

  • apify-api/openapi/components/schemas/actors/ActorDefinition.yaml:44[Apify docs](https://docs.apify.com/storage/dataset-schema) (same text as the already-updated Dataset.yaml)
  • apify-api/openapi/components/objects/datasets/dataset-statistics.yaml:30[field statistics](https://docs.apify.com/storage/dataset-schema/validation#dataset-field-statistics)
  • apify-api/openapi/components/objects/datasets/dataset-items.yaml:445[Dataset schema](https://docs.apify.com/storage/dataset-schema/validation)
  • apify-api/openapi/components/schemas/datasets/DatasetStatistics.yaml:8 → both links to https://docs.apify.com/storage/dataset-schema/validation (and …/validation#dataset-field-statistics)

Equally fine to leave as-is and handle in a separate follow-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Information architecture follow ups

3 participants