feat: add ability to archive data sources#1033
Merged
Conversation
stevenle
changed the title
jeremydw
approved these changes
Apr 15, 2026
Member
jeremydw
left a comment
jeremydw
left a comment
There was a problem hiding this comment.
changes LGTM, wondering if we should have any sort of affordance or changed behavior when accessing a data source that's archived (log message?)
Member
Author
|
we should have a new mandate called "all your comments need to be in the form of a prompt" let me ask claude to log a warning when accessing an archived data source. |
Data sources can now be archived when no longer needed, mirroring the existing release archive pattern. Archived data sources are hidden from the default active view, and sync/publish operations are blocked for archived sources (both client-side and server-side). - Add archivedAt/archivedBy fields to DataSource interface (core + ui) - Add archive/unarchive utility functions and RootCMSClient methods - Block sync/publish on archived data sources - Add archive/unarchive toggle button to EditDataSourcePage - Add status filter (active/unpublished/published/archived) and status badge column to DataPage - Disable sync/publish buttons for archived sources in the UI
RootCMSClient.getDataSource() and getFromDataSource() now emit a console.warn when the requested data source is archived, so callers have visibility that they may be reading stale or deprecated data without breaking existing read flows.
stevenle
force-pushed
the
claude/add-data-source-archiving-2gxUj
branch
from
f0ee843 to
03a32da
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds the ability to archive/unarchive data sources and introduces filtering capabilities to the data sources list. Archived data sources cannot be synced or published, and users can toggle between viewing active, unpublished, published, and archived data sources.
Key Changes
archiveDataSource()andunarchiveDataSource()methods to both the client and UI utilities, with corresponding UI controls in the edit pageDataSourceStatusBadgecomponent to display the current status (Archived, Published, or Unpublished) with tooltips showing when and by whom the status was setImplementation Details
useMemoto efficiently compute filtered results based onarchivedAtandpublishedAttimestampstestCanPublish)https://claude.ai/code/session_016agqc7JYmfsw2as5dPMdwm