Admin UI not visible while using @seachable directive

[athulprathap]

Before opening, please confirm:

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

App Id

d188470ikqnhki

Region

No response

Environment name

production

Amplify CLI Version

7.5

If applicable, what version of Node.js are you using?

v15

What operating system are you using?

windows

Browser type?

chrome

Describe the bug

Recently amplify launched a new feature that disables the visual editor if you are using any schema directives, types or parameters that aren’t yet supported in the Visual editor. We have implemented the @searchable on amplify graphql schema, it was running perfectly fine but it is not showing data model in the UI now, and popping out this error “you are using an unsupported directive @searchable”.Admin UI is not working with @searchable directive.The admin UI issue is repeating in other @directives as well

Expected behavior

Admin UI should be properly visible and we should be able to make the edits in the tables even with @searchable directives

Reproduction steps

1. Open the Admin Panel of the project in amplify console 2.Try opening the data models ,make sure that @searchable directive is included in the query

Additional information

No response

[adilahkb]

Hello @athulprathap, thank you for bringing this up. Currently, the visual editor in Studio does not fully support the @searchable directive, hence why it is disabled for your schema. We are working on expanding the visual editor to support this and will let you know when it is available.

[scottmanny]

I am getting the same error but mine is for the @index directive

[charbono]

I am getting the same error but mine is for the @index directive

Same thing for me.

[tomyates]

I am getting the same error but mine is for the @index directive

Same for me

[minirobotdan]

Same re: @index. Literally just generated my first, fairly trivial schema and the UI is no longer available.

[ori9998]

I am getting the same error but mine is for the @index directive

Same Here, the visual editor just stop working. Any suggestions?

[tyarai]

I am getting the same error but mine is for the @index directive

Same thing for me

[wrpeck]

@tyarai and others - similarly to @searchable, we don't support the @index directive today. However, we are working on expanding the Visual Editor to support a number of additional directives, including both of these. This is high on our priority list!

[digihunch]

I am getting this error for @primaryKey directive. Is that going to be supported? @wrpeck

[wrpeck]

@digihunch - yep, we are also working on custom primary key management support for Studio, along with a lot more!

[foobarnes]

Is there any word on the priority of this? The @index directive was added BY Studio when I created my data model in the UI. This has been a big hinderance to some new changes I need to make.