WIP: Loom -> Cap importer (#363) - #2162
Draft
sarthak210107-png wants to merge 1 commit into
Draft
Conversation
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
注册 for free
to join this conversation on GitHub.
Already have an account?
登录 to comment
1 participant
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.
/claim #363
Draft PR to track work on the Loom importer. Added a plan doc (
apps/chrome-extension/docs/loom-import-plan.md) covering how this reuses the existing extension auth flow (chrome.identity+/api/extension) and the existingloom-downloadCDN-resolution logic, plus what still needs building: extension API contract additions, a new backend importer route, aloomVideoIdmigration for idempotent imports, and an in-extension UI.Still WIP — pushing follow-up commits for the actual auth wiring, backend route, migration, and UI next. Opening as draft per the contributing guide so progress is visible early.