If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Problem
We have seen a number of issues come up related to images. Uploading them, editing them, making them available offline, copying them to clipboard, etc...
Onyx does have support for images, but AFAIK nobody has utilized that functionality to build any app features that follow our offline-first paradigm for images.
Overall, I think there's a lot of confusion around this topic (speaking for myself here, so feel free to comment if you disagree), and that leads to potentially disparate approaches or complex code surrounding images.
Solution
As these come up, we see the need for a common, unified approach to handling images, presumably using Onyx. This issue is meant to serve as a tracking issue for all image-related feature requests and bug fixes. We should look for commonality between these features, try to come up with a generalized, future-proof solution that's easy to work with, and implement it via the WN/Design Doc process.
Linked issues
Setting up Caching Issue(s)
Bugs based off caching [Holding on ^]
"Flashing" / Image rerendering [Holding on ^]
New Features
Bugs (in progress - not on hold)
Resolved issues
Follow-up discussions:
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Problem
We have seen a number of issues come up related to images. Uploading them, editing them, making them available offline, copying them to clipboard, etc...
Onyx does have support for images, but AFAIK nobody has utilized that functionality to build any app features that follow our offline-first paradigm for images.
Overall, I think there's a lot of confusion around this topic (speaking for myself here, so feel free to comment if you disagree), and that leads to potentially disparate approaches or complex code surrounding images.
Solution
As these come up, we see the need for a common, unified approach to handling images, presumably using Onyx. This issue is meant to serve as a tracking issue for all image-related feature requests and bug fixes. We should look for commonality between these features, try to come up with a generalized, future-proof solution that's easy to work with, and implement it via the WN/Design Doc process.
Linked issues
Setting up Caching Issue(s)
Bugs based off caching [Holding on ^]
"Flashing" / Image rerendering [Holding on ^]
New Features
Bugs (in progress - not on hold)
FallbackAvatar&FallbackWorkspaceAvatarsvgimages don't show immediately when uploading as avatar #13038Resolved issues
Follow-up discussions: