aws-amplify / aws-amplify/amplify-studio

UI Library component properties with custom types

Open
#422 0 comments 0 reactions 0 assignees View on GitHub
feature-request studio-ui
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**
![image](https://user-images.githubusercontent.com/6607/147860800-653db8f4-abdd-4f0a-a251-43f85fd90c28.png)

Contributor guide

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.