Skip to content

docs: v0.0.68 release notes, workflow output & StateStore docs, mock example naming - #18

Merged
yilmaztayfun merged 1 commit into
mainfrom
f/v0-0-68-docs
Jul 2, 2026
Merged

docs: v0.0.68 release notes, workflow output & StateStore docs, mock example naming#18
yilmaztayfun merged 1 commit into
mainfrom
f/v0-0-68-docs

Conversation

@yilmaztayfun

@yilmaztayfun yilmaztayfun commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Özet

v0.0.68 (vnext milestone 34) release notu eklendi ve yeni özelliklerin (workflow output mapping, serbest payload, StateStoreTask type 17, transition history effective state alanları) bileşen/API dokümanları güncellendi. Ayrıca örneklerdeki gerçeğe yakın tanımlayıcılar (on-burgan//onboarding deeplink'i, onboarding:kyc-main-flow URN'leri, architecture diyagramlarındaki Onboarding domain) güvenlik gerekçesiyle mock isimlerle değiştirildi (mock-app//sample-page, demo:sample-flow, Loan domain).

Etkilenen Bölüm

  • Technical (docs/)
  • Architecture (architecture/)
  • Business (business/)
  • Product (product/)
  • Blog (blog/)
  • Tooling / CI / Config (sidebars.ts)

Dil

  • TR yazıldı
  • EN çevirisi eklendi
  • EN sonradan eklenecek (priority değil)

Local Doğrulama

  • npm run build başarılı (tr + en)
  • npm run start ile gözle kontrol edildi (build çıktısındaki HTML üzerinden doğrulandı: yeni sayfalar üretildi, mock isimler yerinde, eski ifadeler kalmadı)
  • Internal linkler kırık değil (kalan anchor uyarıları eski arşiv yazılarına ait, bu PR ile ilgisiz)

İlgili Phase / Issue

  • vnext v0.0.68 — milestone 34: #785, #790, #788, #792, #793, #784, #787, #789, #791, #794 (burgan-tech/vnext)

Reviewer Notları

  • Release notunda schemaVersion: 0.0.49 yazıyor — yayınlanan @burgan-tech/vnext-schema@0.0.49 paketi workflow output ve task type "17" tanımlarını içeriyor (unpkg üzerinden doğrulandı).
  • business/ ve product/ altındaki kavramsal "onboarding" kullanımları (self-service onboarding, müşteri onboarding süreci vb.) bilinçli olarak korundu — bir sisteme değil genel kavrama işaret ediyorlar.
  • Eski blog yazısı 2026-05-19-v0-0-54-duyuru.md içindeki "stage": "onboarding" örnek değeri "application-review" olarak güncellendi.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features

    • Added support for direct output responses in synchronous workflow calls.
    • Added free-form JSON request support for workflow start and transition endpoints.
    • Introduced a new State Store task with get/set/delete operations.
    • Transition history now includes more visible state details at completion.
  • Bug Fixes

    • Improved stability for nested and long-running workflow flows.
  • Documentation

    • Updated API, workflow, task, and architecture docs with new examples and terminology.

…mock example naming

- v0.0.68 release notu (workflow output mapping, serbest payload,
  StateStoreTask type 17, transition history effective state, subflow fix seti)
- Workflow bileşenine attributes.output alanı ve Output Mapping bölümü (TR+EN)
- Yeni StateStore Task sayfası + task index/sidebar güncellemeleri (TR+EN)
- REST API: serbest payload modu (x-vnext-payload-mode), sync output yanıtı,
  transition history yanıt alanları
- Örneklerdeki gerçeğe yakın tanımlayıcılar mock isimlerle değiştirildi:
  on-burgan//onboarding → mock-app//sample-page, onboarding:kyc-main-flow →
  demo:sample-flow, architecture diyagramlarında Onboarding → Loan domain

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@yilmaztayfun
yilmaztayfun requested a review from a team July 2, 2026 20:29
@sourcery-ai

sourcery-ai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Reviewer's Guide

This PR adds v0.0.68 release documentation and updates REST/workflow/task/component docs to cover workflow output mapping, free-form payloads, StateStoreTask type 17, and transition history effective-state fields, while also replacing realistic onboarding examples with neutral mock/demo naming and wiring the new task into navigation.

Sequence diagram for workflow output mapping on sync responses

sequenceDiagram
    actor Client
    participant OrchestrationApi
    participant WorkflowEngine
    participant OutputScript

    Client->>OrchestrationApi: POST /workflows/{wf}/instances/start?sync=true
    OrchestrationApi->>WorkflowEngine: StartInstance
    WorkflowEngine-->>WorkflowEngine: Load workflow.attributes.output
    alt output mapping configured
        WorkflowEngine->>OutputScript: IOutputHandler.Execute
        alt script success
            OutputScript-->>WorkflowEngine: body + statusCode + headers
            WorkflowEngine-->>OrchestrationApi: mapped HTTP response
        else script failure
            OutputScript-->>WorkflowEngine: error
            WorkflowEngine-->>OrchestrationApi: StartInstanceOutput
        end
    else no output mapping
        WorkflowEngine-->>OrchestrationApi: StartInstanceOutput
    end
    OrchestrationApi-->>Client: HTTP response
Loading

Sequence diagram for StateStoreTask interactions with Dapr state store

sequenceDiagram
    participant WorkflowInstance
    participant StateStoreTask
    participant DaprStateStore

    WorkflowInstance->>StateStoreTask: Execute TaskType 17 (command = set)
    StateStoreTask-->>StateStoreTask: Prefix key with custom:
    StateStoreTask->>DaprStateStore: SaveStateAsync(storeName, key, value, ttlInSeconds)
    DaprStateStore-->>StateStoreTask: success + ETag
    StateStoreTask-->>WorkflowInstance: Data + Metadata(ETag, Key)

    WorkflowInstance->>StateStoreTask: Execute TaskType 17 (command = get)
    StateStoreTask->>DaprStateStore: GetStateAndETagAsync(storeName, key)
    DaprStateStore-->>StateStoreTask: value or null + ETag
    StateStoreTask-->>WorkflowInstance: Data + Metadata(Found, ETag, Key)
Loading

Flow diagram for payload mode resolution on start/transition

flowchart TD
    R[Request body + headers] --> H{x-vnext-payload-mode header}
    H -->|raw| RAW[Mode = raw]
    H -->|standard| STD[Mode = standard]
    H -->|missing| M[Check top-level attributes key]

    RAW --> N1[Normalize as free-form JSON]
    STD --> N2[Bind as standard DTO]

    M -->|attributes present| N2
    M -->|attributes missing| N1

    N1 --> O1["Wrap as { attributes: ... }"]
    N2 --> O2[Use attributes as-is]

    O1 --> B[Bind StartInstanceInput / TransitionInput]
    O2 --> B
Loading

File-Level Changes

Change Details Files
Document workflow free-form payload support and sync output mapping behavior in REST API and workflow component docs.
  • Add tip section describing free-form JSON payloads and x-vnext-payload-mode header semantics for start and transition endpoints.
  • Document that when a workflow defines attributes.output and sync=true, the HTTP response body comes directly from the output script instead of the standard envelope, with subflows excluded and fallback on errors.
  • Expose output as an optional workflow attribute in the capability/field tables and add dedicated Output Mapping sections in TR and EN workflow docs, cross-linking from async/sync how-to.
docs/api-reference/rest-api.md
docs/components/workflow.md
i18n/en/docusaurus-plugin-content-docs/current/components/workflow.md
docs/how-to/async-sync.md
Introduce and wire documentation for the new StateStore task (TaskType 17) and update task type lists.
  • Increase documented task-type counts and append StateStoreTask with link/description in TR and EN task index pages.
  • Create detailed State Store Task pages in TR and EN explaining config fields, commands (get/set/delete), custom: key prefixing, TTL, concurrency/consistency semantics, and examples.
  • Add the new StateStore task doc to the sidebar navigation so it appears under components/tasks.
docs/components/tasks/index.md
i18n/en/docusaurus-plugin-content-docs/current/components/tasks/index.md
docs/components/tasks/state-store.md
i18n/en/docusaurus-plugin-content-docs/current/components/tasks/state-store.md
sidebars.ts
Enhance transition history documentation to include effective state snapshot fields and their semantics.
  • Extend the transition history endpoint section with a field table for effectiveState, effectiveStateType, effectiveStateSubType, and stage, and note snapshot timing and null behavior for failed/legacy transitions.
  • Clarify that these fields reflect externally visible state at transition completion and are not backfilled for pre-v0.0.68 records.
docs/api-reference/rest-api.md
Add v0.0.68 release notes blog entry with detailed feature and fix descriptions, schema version, and issue references.
  • Create a new blog post describing workflow output mapping, free-form payloads, StateStore task, effective-state history, and subflow stability fixes, tied to schemaVersion 0.0.49.
  • Include configuration snippet, image/provenance note, and per-issue sections summarizing behavior changes.
  • List referenced GitHub issues and provide a concise summary section for the release.
blog/2026-07-02-v0-0-68.md
Sanitize example domain/flow/deeplink naming from onboarding-specific to generic demo/mock names across docs and architecture diagrams.
  • Update URN catalog examples in TR and EN from onboarding:kyc-main-flow to demo:sample-flow, including function URN formats and HTTP equivalents.
  • Change deeplink examples from on-burgan//onboarding to mock-app//sample-page in view component and URN docs and related how-to examples.
  • Adjust architecture and data docs (TR and EN) to use Loan domain and loan_* schemas instead of Onboarding, including mermaid diagrams and explanatory text.
  • Update workflow component tag example from onboarding to account-opening and CLI docs domain profile examples from onboarding/demo-app to demo.
  • Change an old blog example stage value from onboarding to application-review and an action URN in view-consept/aksiyonlar.md to demo:sample-flow.
docs/components/urn-catalog.md
i18n/en/docusaurus-plugin-content-docs/current/components/urn-catalog.md
docs/components/view.md
docs/tools/workflow-cli.md
architecture/domain-model/topology.md
i18n/en/docusaurus-plugin-content-docs-architecture/current/domain-model/topology.md
architecture/data/database.md
i18n/en/docusaurus-plugin-content-docs-architecture/current/data/database.md
architecture/domain-model/index.md
architecture/overview/index.md
blog/2026-05-19-v0-0-54-duyuru.md
docs/how-to/view-consept/aksiyonlar.md
docs/components/workflow.md
i18n/en/docusaurus-plugin-content-docs/current/components/workflow.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This PR adds v0.0.68 release documentation covering workflow output mapping, free-form JSON payloads, a new StateStore task type, and transition history snapshot fields, with corresponding REST API and component doc updates. It also renames example domain/flow identifiers (onboarding to loan/demo) across architecture diagrams and doc examples in both default and English i18n content trees.

Changes

v0.0.68 Feature Documentation

Layer / File(s) Summary
v0.0.68 release blog post
blog/2026-07-02-v0-0-68.md
Adds a new release post documenting features, fixes, config updates, issues, and summary for v0.0.68.
Output mapping documentation
docs/components/workflow.md, docs/how-to/async-sync.md, i18n/en/.../components/workflow.md
Documents attributes.output behavior for sync responses in workflow docs and adds a corresponding async-sync tip.
REST API payload and history docs
docs/api-reference/rest-api.md
Documents free-form JSON payload handling and expanded transition history fields (effectiveState*, stage).
StateStore task documentation and wiring
docs/components/tasks/index.md, docs/components/tasks/state-store.md, sidebars.ts, i18n/en/.../components/tasks/*
Introduces StateStore task (type 17) docs, updates task counts/tables, and adds the sidebar entry.

Estimated code review effort: 2 (Simple) | ~12 minutes

Example domain/flow naming updates

Layer / File(s) Summary
Architecture diagram naming
architecture/data/database.md, architecture/domain-model/topology.md, i18n/en/.../data/database.md, i18n/en/.../domain-model/topology.md
Renames onboarding/customer-onboarding examples to loan naming in Mermaid diagrams.
Domain model example text
architecture/domain-model/index.md, architecture/overview/index.md
Replaces onboarding with kredi in domain example lists.
URN catalog, view, actions, CLI examples
docs/components/urn-catalog.md, docs/components/view.md, docs/components/workflow.md, docs/how-to/view-consept/aksiyonlar.md, docs/tools/workflow-cli.md, i18n/en/.../urn-catalog.md
Updates example URNs, deeplink paths, tags, and CLI commands to demo/sample-flow naming.
Blog JSON example update
blog/2026-05-19-v0-0-54-duyuru.md
Updates example JSON stage value from onboarding to application-review.

Estimated code review effort: 1 (Trivial) | ~8 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main documentation updates: release notes, workflow output/StateStore docs, and mock example renaming.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch f/v0-0-68-docs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • The new workflow output mapping behavior is now described in multiple places (REST API, workflow component, async/sync how-to); consider trimming these to a single authoritative section (e.g., workflow → Output Mapping) and referencing it elsewhere to avoid future divergence in edge-case behavior descriptions.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new workflow `output` mapping behavior is now described in multiple places (REST API, workflow component, async/sync how-to); consider trimming these to a single authoritative section (e.g., workflow → Output Mapping) and referencing it elsewhere to avoid future divergence in edge-case behavior descriptions.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation to reflect the release of v0.0.68, which introduces workflow output mapping for synchronous responses, free-form payload support, a new StateStore task (Type 17) for Dapr state store caching, and effective state snapshots in transition history. It also replaces onboarding examples with loan or demo across several architecture and component documents. The review feedback highlights a translation discrepancy in the Related section of the State Store task documentation between the Turkish and English versions, suggesting that both Dapr Binding and Dapr PubSub tasks be referenced in both languages for consistency.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

## İlgili

- [Tasks Genel Bakış](/docs/components/tasks/) — task türleri ve referans mekanizması
- [Dapr Binding Task](/docs/components/tasks/dapr-binding) — diğer Dapr tabanlı task türleri

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Türkçe ve İngilizce dokümanlar arasında "İlgili" (Related) bölümündeki Dapr görev referanslarında tutarsızlık bulunuyor. Türkçe versiyonda Dapr Binding Task (dapr-binding) referans gösterilmişken, İngilizce versiyonda Dapr PubSub Task (dapr-pubsub) referans gösterilmiş. Her iki dilde de tutarlı olması için her iki görevi de listelemek daha faydalı olacaktır.

Suggested change
- [Dapr Binding Task](/docs/components/tasks/dapr-binding) — diğer Dapr tabanlı task türleri
- [Dapr Binding Task](/docs/components/tasks/dapr-binding) — diğer Dapr tabanlı task türleri
- [Dapr PubSub Task](/docs/components/tasks/dapr-pubsub) — diğer Dapr tabanlı task türleri

## Related

- [Tasks Overview](/docs/components/tasks/) — task types and the reference mechanism
- [Dapr PubSub Task](/docs/components/tasks/dapr-pubsub) — other Dapr-based task types

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Türkçe ve İngilizce dokümanlar arasında "İlgili" (Related) bölümündeki Dapr görev referanslarında tutarsızlık bulunuyor. İngilizce versiyonda Dapr PubSub Task (dapr-pubsub) referans gösterilmişken, Türkçe versiyonda Dapr Binding Task (dapr-binding) referans gösterilmiş. Her iki dilde de tutarlı olması için her iki görevi de listelemek daha faydalı olacaktır.

Suggested change
- [Dapr PubSub Task](/docs/components/tasks/dapr-pubsub) — other Dapr-based task types
- [Dapr Binding Task](/docs/components/tasks/dapr-binding) — other Dapr-based task types
- [Dapr PubSub Task](/docs/components/tasks/dapr-pubsub) — other Dapr-based task types

@yilmaztayfun yilmaztayfun self-assigned this Jul 2, 2026
@yilmaztayfun
yilmaztayfun merged commit 6563b9c into main Jul 2, 2026
3 of 4 checks passed

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@blog/2026-07-02-v0-0-68.md`:
- Around line 104-106: The markdown fence for the API route example is missing
an explicit language, causing the MD040 lint issue. Update the fenced block in
the release note snippet to use a clear language tag such as http or text,
keeping the endpoint example itself unchanged and making sure the surrounding
markdown in the document stays valid.

In `@docs/components/tasks/state-store.md`:
- Around line 1-5: Add the missing documentation frontmatter fields for the
State Store page by updating the existing frontmatter block in state-store.md to
include both id and sidebar_label alongside title; keep the current content
intact and ensure the values are consistent with the page’s purpose so it
satisfies the repo’s docs guideline for markdown pages.

In
`@i18n/en/docusaurus-plugin-content-docs/current/components/tasks/state-store.md`:
- Around line 1-5: The frontmatter for the State Store Task page is missing the
mirrored metadata required for translated docs. Update the frontmatter in the
State Store doc to include the original Turkish page’s id and slug, and add
sidebar_label alongside the existing title so it matches the docs metadata
contract. Keep the change in the frontmatter block for the State Store task
document.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8501ee75-fcff-44b8-8cfb-d609003c5ceb

📥 Commits

Reviewing files that changed from the base of the PR and between 440d4b4 and 310d4b0.

📒 Files selected for processing (22)
  • architecture/data/database.md
  • architecture/domain-model/index.md
  • architecture/domain-model/topology.md
  • architecture/overview/index.md
  • blog/2026-05-19-v0-0-54-duyuru.md
  • blog/2026-07-02-v0-0-68.md
  • docs/api-reference/rest-api.md
  • docs/components/tasks/index.md
  • docs/components/tasks/state-store.md
  • docs/components/urn-catalog.md
  • docs/components/view.md
  • docs/components/workflow.md
  • docs/how-to/async-sync.md
  • docs/how-to/view-consept/aksiyonlar.md
  • docs/tools/workflow-cli.md
  • i18n/en/docusaurus-plugin-content-docs-architecture/current/data/database.md
  • i18n/en/docusaurus-plugin-content-docs-architecture/current/domain-model/topology.md
  • i18n/en/docusaurus-plugin-content-docs/current/components/tasks/index.md
  • i18n/en/docusaurus-plugin-content-docs/current/components/tasks/state-store.md
  • i18n/en/docusaurus-plugin-content-docs/current/components/urn-catalog.md
  • i18n/en/docusaurus-plugin-content-docs/current/components/workflow.md
  • sidebars.ts

Comment on lines +104 to +106
```
GET /api/v1/{domain}/workflows/{workflow}/instances/{instance}/transitions
```

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Specify a fence language.

The bare fence here triggers MD040 and makes the markdown lint output noisy. Use an explicit language such as http or text.

🛠️ Proposed fix
-```
+```http
 GET /api/v1/{domain}/workflows/{workflow}/instances/{instance}/transitions
-```
+```
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
```
GET /api/v1/{domain}/workflows/{workflow}/instances/{instance}/transitions
```
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 104-104: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@blog/2026-07-02-v0-0-68.md` around lines 104 - 106, The markdown fence for
the API route example is missing an explicit language, causing the MD040 lint
issue. Update the fenced block in the release note snippet to use a clear
language tag such as http or text, keeping the endpoint example itself unchanged
and making sure the surrounding markdown in the document stays valid.

Source: Linters/SAST tools

Comment on lines +1 to +5
---
sidebar_position: 13
title: State Store Task
description: Dapr state store üzerinden cache okuma/yazma/silme yapan task
---

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

Add the required frontmatter fields.

This page is missing id and sidebar_label, which are required by the repo's documentation guidelines.

As per coding guidelines, **/{docs,architecture,business,product}/**/*.{md,mdx}: Every documentation page must include frontmatter with at minimum: id, title, and sidebar_label fields.

🛠️ Proposed fix
 ---
+id: state-store
 sidebar_position: 13
 title: State Store Task
+sidebar_label: State Store Task
 description: Dapr state store üzerinden cache okuma/yazma/silme yapan task
 ---
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
sidebar_position: 13
title: State Store Task
description: Dapr state store üzerinden cache okuma/yazma/silme yapan task
---
---
id: state-store
sidebar_position: 13
title: State Store Task
sidebar_label: State Store Task
description: Dapr state store üzerinden cache okuma/yazma/silme yapan task
---
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/components/tasks/state-store.md` around lines 1 - 5, Add the missing
documentation frontmatter fields for the State Store page by updating the
existing frontmatter block in state-store.md to include both id and
sidebar_label alongside title; keep the current content intact and ensure the
values are consistent with the page’s purpose so it satisfies the repo’s docs
guideline for markdown pages.

Source: Coding guidelines

Comment on lines +1 to +5
---
sidebar_position: 13
title: State Store Task
description: Task that reads, writes, and deletes cache entries via a Dapr state store
---

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add the missing mirror frontmatter fields.

This page still needs id and sidebar_label, so it doesn't satisfy the docs metadata contract for mirrored pages yet. As per coding guidelines, every documentation page must include frontmatter with at minimum id, title, and sidebar_label fields, and English translations must preserve the original Turkish id and slug.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@i18n/en/docusaurus-plugin-content-docs/current/components/tasks/state-store.md`
around lines 1 - 5, The frontmatter for the State Store Task page is missing the
mirrored metadata required for translated docs. Update the frontmatter in the
State Store doc to include the original Turkish page’s id and slug, and add
sidebar_label alongside the existing title so it matches the docs metadata
contract. Keep the change in the frontmatter block for the State Store task
document.

Source: Coding guidelines

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant