aws-amplify / aws-amplify/amplify-studio

In the content editing page of the amplify studio, you cannot edit nested custom types

Open
#668 2 comments 0 reactions 0 assignees View on GitHub
cms feature-request studio-ui
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.

### App Id

_No response_

### Region

ap-northeast-1

### Environment name

658

### 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

In the content editing page of the amplify studio, you cannot edit nested custom types, such as
product ->commission (custom type) ->price (custom type).
When editing a product, you cannot edit the price in the commission.

### Expected behavior

product ->commission (custom type) ->price (custom type).
When editing a product, I can edit the price in the commission.

### Reproduction steps

1、create product model
2、create commission field in product, type is custom
3、create price field in commission,type is custom
4、in content edit,add a product
5、can eidt commission,but cannot edit price in commission.

### Project Identifier

3a960a7a629c6e2035a26964f531400f

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in the Amplify Studio content editing page using the product → commission custom type → price custom type model described in the steps. Start by tracing how nested custom-type fields are rendered and edited; done means the price field can be edited when creating or editing a product.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.