Skip to content

Conversation

@arpandhakal
Copy link
Collaborator

@arpandhakal arpandhakal commented Jan 15, 2026

Changes

  • created a mechanism to support creating entries on attachments tables based on files/images uploaded on
    • task creation
    • task description update
    • subtask creation
    • subtask description update
    • comment/reply creation
    • comment/reply update
  • Entries on attachments table are done from api services when task/comments are created and from fronend client components when tasks/comments are edited.
  • Remaining: Clean deleted attachments from attachments table while clearing out scrap medias
  • General refactoring

Testing

@arpandhakal arpandhakal self-assigned this Jan 15, 2026
@linear
Copy link

linear bot commented Jan 15, 2026

@vercel
Copy link
Contributor

vercel bot commented Jan 15, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
tasks-app Ready Ready Preview, Comment Jan 20, 2026 9:24am

Request Review

- created a mechanism to support creating entries on attachments tables based on files/images uploaded on
	- task creation
	- task description update
	- subtask creation
	- subtask description update
	- comment/reply creation
	- comment/reply update
- Entries on attachments table are done from api services when task/comments are created and from fronend client components when tasks/comments are edited.
- Remaining: Clean deleted attachments from attachments table while clearing out scrap medias
- added a mechanism to extract attachments when comment/reply is created, move them to their respective folder and create an entry on attachments table.
- Cleaning deleted attachments from attachments table while clearing out scrap medias.
…on issues. totally segregated replies/comments to have their own attachment entities
…on issues. totally segregated replies/comments to have their own attachment entities
}
setLastUpdated(task?.lastActivityLogUpdated)
}
}, [task?.lastActivityLogUpdated])
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's also suppress these warning if they are intentional.

Copy link
Collaborator

@SandipBajracharya SandipBajracharya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see we have drilled postAttachment() prop up to 4 levels. Is there any way we can refactor this? Maybe use context in this case if possible?

Copy link
Collaborator

@SandipBajracharya SandipBajracharya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please include the testing criteria

Copy link
Collaborator

@SandipBajracharya SandipBajracharya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In createUploadFn(), do we need to check for config.workspace and return undefined if not found? I saw condition check for token && tokenPayload.workspace before the refactor.

Everything else LGTM 🙌

…achment. workspaceId is needed for building folder structure effecting filePaths
@arpandhakal arpandhakal merged commit 1a1bcbb into feature/api-improvements Jan 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants