microsoft / microsoft/TypeChat

ChatGPT interpretes prompt as wanting and example of JSON, not JSON with actual data for the user request

Open
#79 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
8.7k
Forks
414
Avg merge
3h 8m
Merged PRs (30d)
3

Description

Hello

I've been playing around with a meal plan app for which I've been working a lot on how to get ChatGPT to give the result as JSON.
For this reason, when I heard about TypeChat, I thought that, that sounded like a perfect solution.

Not sure whether its due to my type definitions are a bit complex, but the resulting prompts make ChatGPT interpret that I want an example on how a resulting JSON could look.

Here's a link to a chat I made with the prompt generated by Typechat.

https://chat.openai.com/share/5bce537a-f9b8-4fbc-afd7-7ebb724b3f89

In my own approach I've had success with ending my prompt with the type definition. Like for example:

"Your response should be in JSON format {meals: {"description": string, "ingredients": {"name": string, "quantity": number, "unit": string}[], "directions": string[]}[]}."

Have you considered this sort of approach?

Contributor guide

No contributing guide indexed for this repository

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 reviewing the generated TypeChat prompt and the linked ChatGPT conversation, then compare the requested meal-plan output with the type definitions and prompt wording described here. Done would mean agreeing on a reproducible prompt-generation change or confirming the expected approach for requesting actual user data rather than an example JSON shape.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.