aws-amplify / aws-amplify/amplify-studio
UI Library component properties with custom types
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
You can have custom types (== types without @model directive) in graphql api, but cant use them in UI Library component properties.
Component properties can be only of model or scalar types.
**Describe the solution you'd like**
It would be very useful to have component properties with custom types, too.
**Additional context**

Contributor guide
Research direction
Start in the UI Library component-property flow and reproduce the issue with a GraphQL API custom type that lacks the @model directive. Trace where property types are limited to models or scalars; done means custom GraphQL types can be selected and used as component properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100