aws-amplify / aws-amplify/amplify-studio
Changing bound data model not reflected in collection preview
- 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
d3h9zzjvrhf7sf
### Region
eu-west-2
### 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
If I bind a component to one data model, create a collection from it, and go back to the component to bind it to another model, it is not reflected in the collection preview.
### Expected behavior
The collection preview updates with the right model.
### Reproduction steps
See video
https://user-images.githubusercontent.com/73264629/232641730-a3d35f7a-4991-41ce-a35f-66005d8fb8e4.mov
### Project Identifier
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Start by following the linked reproduction video and reproduce the sequence of binding a component to one data model, creating a collection, then switching the component to another model. Trace the component binding and collection preview entry points to find where the model selection is retained. Done means the collection preview updates to show the newly bound model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100