aws-amplify / aws-amplify/amplify-studio
UI Library Collections should accept properties
- Dominant language
- No language data
- Stars
- 135
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the feature you'd like to request
I'd like to define component properties for Collections, the same way I can for Components. Then, when the ui-component for the collection is autogenerated, I can pass properties into it, and it will filter/sort by the data in my property.
### Describe your use case and how the feature would improve your experience.
I have a lot of models in my Amplify Studio, linked together with one-to-many relationships. I want to create Collection components which display all "many" entities related to my "one" related entity id. For instance, I have a Conversation, with many Messages. I'd like to create a MessageList collection, and I'd like to add a filter by message.conversationID, but this only allows me to pass static values. This prevents me from making a collection component I can simply pass a conversation or conversationID into.
### Describe alternatives you've considered
Currently, I'm not using Collections, and instead listing these manually in the react code. I'd like to benefit from pagination, sort, search, and all the other benefits of using the auto-generated collections.
### Additional context
_No response_
Contributor guide
Research direction
Start with the UI Library Collections generation path and the React usage described in the issue. Check how collection filters currently accept static values, then define done as allowing a generated collection to receive a conversation or conversationID for filtering while retaining pagination, sorting, and search.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100