Updated MessageChannelSyncStatus enum: changed COMPLETED to ACTIVE

[akarsanth]

Fixes #5961

[greptile-apps]

PR Summary

• Renamed MessageChannelSyncStatus.COMPLETED to ACTIVE
• Updated references to COMPLETED status throughout the codebase

_{1 file(s) reviewed, no comment(s)}

[greptile-apps]

PR Summary

(updates since last review)

• Renamed COMPLETED status to ACTIVE in MessageChannelSyncStatus enum
• Updated database command to reflect the new ACTIVE status
• Modified field metadata options to include ACTIVE status
• Ensured consistency in naming convention across database and application logic

_{2 file(s) reviewed, no comment(s)}

[greptile-apps]

PR Summary

(updates since last review)

• Updated MessageChannelSyncStatus enum: changed COMPLETED to ACTIVE
• Modified markAsCompletedAndSchedulePartialMessageListFetch method to reflect the new status
• Ensured correct status update in the message channel repository

_{1 file(s) reviewed, no comment(s)}

[greptile-apps]

PR Summary

(updates since last review)

• Updated MessageChannelSyncStatus enum: replaced COMPLETED with ACTIVE
• Modified database schema to reflect new enum values
• Updated syncStatus field metadata in messageChannel table
• Adjusted updateSyncStatus method logic in message-channel.repository.ts

_{2 file(s) reviewed, no comment(s)}

[charlesBochet]

Thanks for contributing @akarsanth :) Seems the ticket is already assigned to another contributor but the contributor has not raised a PR yet
If the contributor has not created a PR tonight (within the 3 days window), I'll review this one

[charlesBochet]

Hi @akarsanth Thanks for the PR!
It's great to remove COMPLETED to ACTIVE but it's not sufficient as for existing workspace, we will need to also rename COMPLETE to ACTIVE messageChannels.

Could you create a command (see 0-20-update-message-channel-sync-status-enum.command for example) thats:

• loop over all existing workspaces (or takes a workspace as a parameter)
• update the corresponding fieldMetadata in database
• update the corresponding enum and data in workspace schema.
• => this is very close to the example command

[charlesBochet]

(and the command should be name as 0-21 now as we are preparing the 0.21 version)

[charlesBochet]

LGTM, thank you @akarsanth @bosiraphael :)

[github-actions]

Thanks @akarsanth for your contribution!
This marks your 0th PR on the repo. You're top 0% of all our contributors 🎉
See contributor page - Share on LinkedIn - Share on Twitter