Fix context-menu and documents

Author: fcollonval

command-palette/ui-tests/README.md

@@ -19,7 +19,7 @@ jlpm run build:prod
 2. Execute the docker stack in the example folder:
 
 ```
-docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build
+docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build --no-cache
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env run --rm e2e
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env down
 ```
@@ -107,7 +107,7 @@ docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.
 jupyter lab --ServerApp.token= --ServerApp.password=
 ```
 
-3. Launch the code generator tool:
+3. Launch the debug tool:
 
 ```
 cd ui-tests

commands/ui-tests/README.md

@@ -19,7 +19,7 @@ jlpm run build:prod
 2. Execute the docker stack in the example folder:
 
 ```
-docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build
+docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build --no-cache
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env run --rm e2e
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env down
 ```
@@ -107,7 +107,7 @@ docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.
 jupyter lab --ServerApp.token= --ServerApp.password=
 ```
 
-3. Launch the code generator tool:
+3. Launch the debug tool:
 
 ```
 cd ui-tests

completer/ui-tests/README.md

@@ -19,7 +19,7 @@ jlpm run build:prod
 2. Execute the docker stack in the example folder:
 
 ```
-docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build
+docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build --no-cache
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env run --rm e2e
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env down
 ```
@@ -107,7 +107,7 @@ docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.
 jupyter lab --ServerApp.token= --ServerApp.password=
 ```
 
-3. Launch the code generator tool:
+3. Launch the debug tool:
 
 ```
 cd ui-tests

context-menu/README.md

@@ -69,15 +69,15 @@ You will need to define a context menu item under the property `context` of the
   "context": [
     {
       "command": "jlab-examples/context-menu:open",
-      "selector": ".jp-DirListing-item[data-file-type=\"example\"]",
+      "selector": ".jp-DirListing-item[data-file-type=\"text\"]",
       "rank": 0
     }
   ]
 },
 ```
 <!-- prettier-ignore-end -->
 
-The `selector` can be any valid [CSS selector](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors). In this case, the first part is the CSS class that identifies the file browser items `.jp-DirListing-item` and the second part `[data-file-type="example"]` is a attribute value to be found on the item; the `data-file-type` attribute is set with the file extension. You can omit the second part to add the command to every file type.
+The `selector` can be any valid [CSS selector](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Selectors). In this case, the first part is the CSS class that identifies the file browser items `.jp-DirListing-item` and the second part `[data-file-type="text"]` is a attribute value to be found on the item; the `data-file-type` attribute is set with the file type name or `text` for generic files. You can omit the second part to add the command to every file type.
 
 You can find some of the CSS classes that identify different widgets in JupyterLab in the [developer documentation](https://jupyterlab.readthedocs.io/en/stable/developer/css.html#commonly-used-css-selectors).
 

context-menu/schema/plugin.json

@@ -5,7 +5,7 @@
     "context": [
       {
         "command": "jlab-examples/context-menu:open",
-        "selector": ".jp-DirListing-item[data-file-type=\"example\"]",
+        "selector": ".jp-DirListing-item[data-file-type=\"text\"]",
         "rank": 0
       }
     ]

context-menu/ui-tests/README.md

@@ -19,7 +19,7 @@ jlpm run build:prod
 2. Execute the docker stack in the example folder:
 
 ```
-docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build
+docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build --no-cache
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env run --rm e2e
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env down
 ```
@@ -107,7 +107,7 @@ docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.
 jupyter lab --ServerApp.token= --ServerApp.password=
 ```
 
-3. Launch the code generator tool:
+3. Launch the debug tool:
 
 ```
 cd ui-tests

context-menu/ui-tests/tests/context-menu.spec.ts

@@ -35,14 +35,7 @@ test('should have new context menu for example files', async ({ page }) => {
   await page.press('input.jp-DirListing-editor', 'Enter');
 
   // Wait for the data attribute to be set
-  let resolveImmediate;
-  const waitForImmediate = new Promise((resolve) => {
-    resolveImmediate = resolve;
-  });
-  setImmediate(() => {
-    resolveImmediate();
-  });
-  await waitForImmediate;
+  await page.waitForTimeout(200);
 
   // Click [aria-label="File Browser Section"] >> text=test.example
   await page.click('[aria-label="File Browser Section"] >> text=test.example', {

custom-log-console/ui-tests/README.md

@@ -19,7 +19,7 @@ jlpm run build:prod
 2. Execute the docker stack in the example folder:
 
 ```
-docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build
+docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build --no-cache
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env run --rm e2e
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env down
 ```
@@ -107,7 +107,7 @@ docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.
 jupyter lab --ServerApp.token= --ServerApp.password=
 ```
 
-3. Launch the code generator tool:
+3. Launch the debug tool:
 
 ```
 cd ui-tests

datagrid/ui-tests/README.md

@@ -19,7 +19,7 @@ jlpm run build:prod
 2. Execute the docker stack in the example folder:
 
 ```
-docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build
+docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env build --no-cache
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env run --rm e2e
 docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.env down
 ```
@@ -107,7 +107,7 @@ docker-compose -f ../end-to-end-tests/docker-compose.yml --env-file ./ui-tests/.
 jupyter lab --ServerApp.token= --ServerApp.password=
 ```
 
-3. Launch the code generator tool:
+3. Launch the debug tool:
 
 ```
 cd ui-tests

documents/README.md

@@ -56,7 +56,7 @@ At the same time, you need to implement the method `createNew`. The `DocumentMan
 
 <!-- prettier-ignore-start -->
 ```ts
-// src/factory.ts#L100-L102
+// src/factory.ts#L109-L111
 
 createNew(languagePreference?: string, modelDB?: IModelDB): ExampleDocModel {
   return new ExampleDocModel(languagePreference, modelDB);
@@ -157,7 +157,7 @@ To create a new shared object, you have to use the `ydoc`. The new attribute wil
 
 <!-- prettier-ignore-start -->
 ```ts
-// src/model.ts#L327-L328
+// src/model.ts#L340-L341
 
 this._content = this.ydoc.getMap('content');
 this._content.observe(this._contentObserver);
@@ -168,15 +168,15 @@ To access the information about the different users connected, you can use the `
 
 <!-- prettier-ignore-start -->
 ```ts
-// src/model.ts#L261-L261
+// src/model.ts#L279-L279
 
 this.sharedModel.awareness.setLocalStateField('mouse', pos);
 ```
 <!-- prettier-ignore-end -->
 
 <!-- prettier-ignore-start -->
 ```ts
-// src/model.ts#L289-L289
+// src/model.ts#L302-L302
 
 const clients = this.sharedModel.awareness.getStates();
 ```
@@ -194,7 +194,7 @@ Every time you modify a shared property, this property triggers an event in all
 
 <!-- prettier-ignore-start -->
 ```ts
-// src/model.ts#L167-L170
+// src/model.ts#L183-L186
 
 this.sharedModel.transact(() => {
   this.sharedModel.setContent('position', { x: obj.x, y: obj.y });