aws-amplify / aws-amplify/amplify-studio
Admin UI not visible while using @seachable directive
- 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.
### 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_
Contributor guide
Research direction
Reproduce the issue by opening the Amplify Admin Panel data models for a project whose GraphQL schema includes @searchable, using the reported reproduction steps. Check how the Admin UI handles unsupported directives and confirm the expected result: the data model should remain visible and table edits should work.】【。
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, graphql, node.js
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100