Component name clashing with native library cause page to hang and there's no way to delete it

[Yangobears]

Before opening, please confirm:

• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

dlperh6l8tubt

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?

v16.17.1

What operating system are you using?

linux

Browser type?

chrome

Describe the bug

So I accidentally name a Figma component called "Text" - not knowing Text is a primitive component in

import` { Flex, Text } from "@aws-amplify/ui-react";

My component is being created, when I click that component on the admin UI, the page would become unresponsive.
That blocks me from deleting this component.
Is there a way to delete this component from admin so "amplify pull" won't pull it cause build errors (due to name clashing again)

Expected behavior

• component shouldn't be created/ or should be created with a rename to avoid clashing with the one from @aws-amplify/ui-react
• I should be able to delete component in admin page/ in some ways.

Reproduction steps

1. Create a component in Figma named "Text"
2. Import
3. You will get a component created, but there's no way to manage/delete that component

Project Identifier

7ce9e49a2c4bf107c0442116d84eeded

Additional information

No response

[scottyoung]

Hi @Yangobears,

Click the Edit button in the UI Library nav section, select the component(s) you wish to delete, and then click Delete selected components in the right hand pane.

[cwoolum]

Hi @Yangobears , we are currently working on a fix that prevent built in primitives from clashing with custom components. We'll update this ticket when the fix has rolled out.

[ykethan]

Closing as this has been fixed.

[github-actions]

⚠️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.