Working with Figma file and UI component generation with multiple environment is causing clobbering

Bryson14 commented 9 months ago

Before creating a new issue, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have tried disabling all browser extensions or using a different browser
[X] I have tried deleting the node_modules folder and reinstalling my dependencies
[X] I have read the guide for submitting bug reports.

On which framework/platform are you having an issue?

React

Which UI component?

Primitive components

How is your app built?

CRA

What browsers are you seeing the problem on?

Chrome

Which region are you seeing the problem in?

us-east-1

Please describe your bug.

i have a figma file that has components I've generated. I connected that figma file both of my dev and main amplify studios. Now they are both in sync with the file, but as you know, you can connect various fields to data and there is some work that happens cleaning up the component within amplify studio.

I have the components and their data working with dev but not in main. So my solution now is whenever i run amplify pull in main, i have to ignore any changes done in the src/ui-components/ directory so it doesn't break the website or show empty data fields. Only the ui components generated form dev are correct in my case, and always are merged over main, before deploying.

Is there a better way to do this? Or is this the intended way to use the ui component generation?Amplify Studio

What's the expected behaviour?

a way to pull over configuration done in one studio to another to not repeat the customizing process for the component.

Help us reproduce the bug!

Make a project with two backend environments.

Create a figma file and component

Import that file into both studio environments.

click "configure" to alter the function of the component within one of the studios, but not the other.

IN your ide, run amplify pull for both environments.

Compare the output of the ui component generated.

Code Snippet

// Put your code below this line.

Console log output

No response

Additional information and screenshots

No response

ykethan commented 9 months ago

Hey @Bryson14, on each amplify pull is expected to pull the components from Amplify Studio and replace the ui-components folder. But if you would like to not pull the components, you can run amplify pull --no-codegen which should skip the component generation.

arundna commented 5 months ago

Closing the issue due to inactivity - This repository only accepts new feature requests for AWS Amplify Studio. For technical support, we encourage you to open a case with AWS technical support if you have AWS support plan. If you do not have an active AWS support plan, we encourage you to leverage our Amplify community Discord server where community members and staff try to help each other with Amplify.

github-actions[bot] commented 5 months ago

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

aws-amplify / amplify-studio