feat(llc): implement attachment uploader

[xsahil03x]

This pull request adds comprehensive support for file and image uploads and deletions via a new CDN client abstraction, and improves how attachments are handled when adding comments. The changes introduce a new CdnClient interface and implementation, update the configuration and client initialization to support custom CDN clients, and enhance the ActivityAddCommentRequest model to better support attachment uploads.

CDN Client Integration and File Management:

• Introduced a new CdnClient interface and a default FeedsCdnClient implementation for handling file and image uploads and deletions, with progress tracking and cancellation support. This includes new methods for uploadFile, uploadImage, deleteFile, and deleteImage in both the API and client layers. [1] [2] [3] [4]
• Updated the main client (StreamFeedsClientImpl) to initialize and expose the CDN client and attachment uploader, and to delegate file/image deletion to the CDN client. [1] [2] [3] [4]

Configuration and Extensibility:

• Enhanced the FeedsConfig model to allow injection of a custom CdnClient, enabling flexible CDN integration. [1] [2]

Attachment Uploads in Comments:

• Expanded the ActivityAddCommentRequest model to include fields for activityId, activityType, and a list of StreamAttachment uploads, improving support for adding comments with file/image attachments. The corresponding mapper and generated code were updated accordingly. [1] [2] [3] [4] [5] [6] [7] [8]

API and Internal Refactoring:

• Refactored the internal API and generated code to rename and adapt upload methods (e.g., sendFile → uploadFile), add progress/cancellation parameters, and support new response types for image uploads and deletions. [1] [2] [3] [4] [5] [6]

These changes collectively make file and image management more robust and extensible, and improve the developer experience when working with attachments in comments.

[renefloor]

Do we just create the activities without attachments if the uploads fail? Shouldn't we return an error in that case?

[renefloor]

I have the feeling this is the exact same code in multiple places, maybe this can also go to the helper class?

[renefloor]

context.client might be different here, so we also have to (re)create the feed object in didChangeDependencies.

[renefloor]

Why do you use AutoRouter here? That's already done by the material app right?

[renefloor]

Another issue here is that this is being called every time you resize the window, as the MediaQuery changes.

In this video you see 429 responses in the logs on the background.

screen.resizing.mov

I think what you want to do here is to only getOrCreate the feed when the current user changes?
So something like this:

  Feed? feed;
  String? currentUserId;

  @override
  void didChangeDependencies() {
    super.didChangeDependencies();
    if (currentUserId != context.currentUser.id) {
      currentUserId = context.currentUser.id;
      feed?.dispose();
      feed = context.client.feedFromQuery(
        FeedQuery(
          fid: FeedId(group: 'user', id: context.currentUser.id),
          data: FeedInputData(
            visibility: FeedVisibility.public,
            members: [FeedMemberRequestData(userId: context.currentUser.id)],
          ),
        ),
      )..getOrCreate();
    }
  }