-
Notifications
You must be signed in to change notification settings - Fork 4
♻️ Simplify attachment previews by conforming Attachment to View
#20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Summary of ChangesHello @YoungHypo, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refactors the attachment preview rendering mechanism by introducing a Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a previewView() method to the Attachment protocol, allowing each attachment type to define its own SwiftUI preview. This is a good architectural improvement that simplifies AttachmentPreviewCard by removing conditional logic. The implementations for ImageAttachment and EmptyAttachment are included. My review includes a couple of suggestions to improve the design's flexibility and adhere to SwiftUI best practices. Specifically, I've noted that hardcoding the frame and style within ImageAttachment.previewView could limit reusability, and I've pointed out a redundant use of AnyView.
|
@peterfriese da4bf21 moved
|
Attachment to View
peterfriese
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, approved!

This PR refactors the Attachment protocol to create a simpler and more idi-omatic SwiftUI API for rendering attachment previews.
The previous design required types conforming to Attachment to implement a previewView() function. The new approach removes this function and instead requires Attachment to conform directly to SwiftUI.View.
This change simplifies the implementation of custom attachments and makes the code in views that render them cleaner and more intuitive.
Key Changes
Attachmentprotocol no longer has apreviewView()requirement and now inherits fromView.AttachmentPreviewCardandMessageComposerViewnow have a simpler generic constraint (<AttachmentType: Attachment & View>) and can render the attachment directly (e.g., attachment) insteadof calling a function (
attachment.previewView()).ImageAttachmentandEmptyAttachmenthave been updated to conform toViewby implementing the required body property.Before
After