dotCMS / dotCMS/core

Support structured output in dotAI responses

Open
#31,325 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Team : Falcon Type : New Functionality
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

No response

User Story

As a front-end dev, I need to provide the output in JSON format of the response I need from dotAI.

For this I need to have available an endpoint that takes the structured output format/schema and use it for the response.

See: https://platform.openai.com/docs/guides/structured-outputs

Acceptance Criteria
  • New or existing endpoint that takes the schema of the structured output and responds accordingly.
  • Postman tests.
Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing dotAI response endpoint and its request handling, then find the Postman test collection used for API coverage. Confirm how structured output schemas should be accepted and passed through; done means the endpoint returns responses matching the supplied schema and the behavior is covered by Postman tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ai, api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.