Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use content providers to remove RTC prefix #418

Merged
merged 14 commits into from
Jan 7, 2025
Merged

Use content providers to remove RTC prefix #418

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
b5cedfc
Use content providers (v2)
krassowski Dec 16, 2024
a7852b5
Reduce the diff
krassowski Dec 16, 2024
1c6e4f3
Rewrite logic which used to rely on RTC prefix, cleanup
krassowski Dec 17, 2024
9f6461d
Update to JupyterLab v4.4.0a2
krassowski Jan 7, 2025
e2c87ad
Align TypeScript version with JupyterLab, re-enable lib check
krassowski Jan 7, 2025
4d72eb1
Fix TypeScript tests
krassowski Jan 7, 2025
160ff53
Bump JupyterLab version used in CI tests
krassowski Jan 7, 2025
756afc8
Bump JupyterLab installed with `dev_install`
krassowski Jan 7, 2025
eb8dc98
Fix "Test Minimum Versions" job
krassowski Jan 7, 2025
279ed6d
Run UI tests on 4.4.0a2 or newer
krassowski Jan 7, 2025
2bf9ac6
Expect the copied link to not have `RTC:` prefix
krassowski Jan 7, 2025
abb234b
Set awareness for user regardless of RTC prefix
krassowski Jan 7, 2025
e17fb88
Match any file, not only files starting with letters
krassowski Jan 7, 2025
4e69d61
Fix opening collaborator's file (remove no-longer needed RTC prefix)
krassowski Jan 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 7 additions & 17 deletions packages/collaborative-drive/src/tokens.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,19 @@
// Copyright (c) Jupyter Development Team.
// Distributed under the terms of the Modified BSD License.

import { DocumentChange, IAwareness, YDocument } from '@jupyter/ydoc';
import { Contents } from '@jupyterlab/services';
import { IAwareness } from '@jupyter/ydoc';
import { Contents, SharedDocumentFactory } from '@jupyterlab/services';
import { IDisposable } from '@lumino/disposable';

import { Token } from '@lumino/coreutils';

/**
* The collaborative drive.
*/
export const ICollaborativeDrive = new Token<ICollaborativeDrive>(
'@jupyter/collaboration-extension:ICollaborativeDrive'
);
export const ICollaborativeContentProvider =
new Token<ICollaborativeContentProvider>(
'@jupyter/collaboration-extension:ICollaborativeContentProvider'
);

/**
* The global awareness token.
Expand All @@ -21,18 +22,7 @@ export const IGlobalAwareness = new Token<IAwareness>(
'@jupyter/collaboration:IGlobalAwareness'
);

/**
* A document factory for registering shared models
*/
export type SharedDocumentFactory = (
options: Contents.ISharedFactoryOptions
) => YDocument<DocumentChange>;

/**
* A Collaborative implementation for an `IDrive`, talking to the
* server using the Jupyter REST API and a WebSocket connection.
*/
export interface ICollaborativeDrive extends Contents.IDrive {
Copy link
Member

Choose a reason for hiding this comment

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

Looks like we'll want to log that somewhere in the changelog as API breaking change, since other extensions may currently depend on ICollaborativeDrive?

For instance it's the case of JupyterCAD and JupyterGIS:

Copy link
Member Author

Choose a reason for hiding this comment

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

It looks like the transition will be smooth because:

  • both extensions used ICollaborativeDrive as an optional dependency (after all it was just added)
  • neither of the extensions actually relied on the Drive part of ICollaborativeDrive - the same properties that they needed will be available on ICollaborativeContentProvider

So when cutting the release we will just need to add a note that migration from ICollaborativeDrive to ICollaborativeContentProvider token for access to shared factory and forks will be required. I do not see a good way to do that right now as the changelog for next version is not there yet - is it ok if we add it during/just after cutting the release?

export interface ICollaborativeContentProvider {
/**
* SharedModel factory for the YDrive.
*/
Expand Down
Loading
Loading