aws-amplify / aws-amplify/amplify-studio
Not consistent code generation
- 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
d3c0uqzq19tdvq
### Region
ap-noertheast-1
### Environment name
amplify ui
### 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
2 months ago. I generated site with amplify + figma.
Now I needed to add small change to my site.
But when I `amplify pull` all components have a this diff.

order of override and rest is changed.
Now some of my component's breakpoint does not work
### Expected behavior
generated code order does not chage.
or breakpoint to work with new generated code
### Reproduction steps
I have no idea
### Project Identifier
_No response_
### Additional information
_No response_
Contributor guide
Research direction
The report names amplify pull, Amplify Studio, Figma-generated components, and a breakpoint regression, but provides no files, tests, versions, or reproduction steps. Start by reproducing the pull for app d3c0uqzq19tdvq and comparing generated component changes before and after the pull. Done means identifying the cause of the ordering change and confirming that generated breakpoints behave consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- figma
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100