aws-amplify / aws-amplify/amplify-studio

auto generate for AWSJson type generated too much data in the field

Open
#925 0 comments 0 reactions 0 assignees View on GitHub
bug cms studio-ui ui-forms
Dominant language
No language data
Stars
135
Forks
32
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

dqdvhtuddlo4i

### Region

us-east-1

### Environment name

staging

### Figma File Version (if applicable)

_No response_

### Amplify CLI Version

_No response_

### If applicable, what version of Node.js are you using?

_No response_

### What operating system are you using?

_No response_

### Browser type?

_No response_

### Describe the bug

using the auto generate on a data model with AWSJson type generated too much

https://github.com/aws-amplify/amplify-studio/assets/87995712/ad055522-419f-44d6-a868-e2beeea67d4b

### Expected behavior

generate an appropriate amount of example data

### Reproduction steps

1. create a model with for example:

```
type User @model @auth(rules: [{allow: public}]) {
id: ID!
status: AWSJSON
}
```
2. open CMS and select auto generate

### Project Identifier

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start in the CMS auto-generate flow using the provided AWSJSON model reproduction. Compare the generated example data for the status field with the expected appropriate amount, and verify the behavior after selecting auto generate.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.