Skip to content

Commit 7e3e845

Browse files
authored
Fix lint errors 🔔 (#796)
1 parent 98d4a97 commit 7e3e845

File tree

4 files changed

+0
-6
lines changed

4 files changed

+0
-6
lines changed

docs/contributor_guide/code_quality.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@ We have several tools configured for checking code quality:
1010
Install checks with `pre-commit install`.
1111
Run them manually with `pre-commit run --all-files`.
1212
**Will exit non-zero when finding errors or changing files.**
13-
1413
- Ruff formats and lints (sometimes autofixes) Python code.
1514

1615
- Generic pre-commit checks help avoid common mistakes like committing large
@@ -21,7 +20,6 @@ We have several tools configured for checking code quality:
2120
Run manually with `jlpm run lint`.
2221
**Will exit 0 when applying fixes.**
2322
**Check the logs and/or `git status` after every run.**
24-
2523
- Prettier formats the file types listed above.
2624

2725
- Eslint lints (sometimes autofixes) JS/TS code.

docs/contributor_guide/troubleshooting.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,11 @@
22

33
- Setup of development environment hangs indefinitely when running the
44
`dev-install.py` step, specifically on the Yarn linking step.
5-
65
- This may be caused by having a `.gitignore` file in your home directory.
76
This is a [known issue with Nx](https://github.com/nrwl/nx/issues/27494).
87
The [only known workaround](https://github.com/nrwl/nx/issues/27494#issuecomment-2481207598) is to remove the `.gitignore` file from your home directory or to work in a location outside of the home directory tree.
98

109
- Every UI test fails after 60 seconds due to timeout.
11-
1210
- This could be caused by having a JupyterLab instance already running at port
1311
`:8888`. Please ensure that there is nothing running at <http://localhost:8888/lab>
1412
before running tests.

docs/user_guide/features/collab.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ One of the standout features of JupyterGIS is its shared editing functionality,
99
If you are using a local installation, your JupyterLab instance is not available to the Internet by default, thus collaborators cannot join your session directly. Here are two techniques to facilitating collaboration in such instances.
1010

1111
1. Hosting a local server using VSCode (Microsoft) or PyCharm (Jetbrains) enables real-time collaboration without exposing your server to the Internet.
12-
1312
- To use VSCode's Live Share, you can follow the steps [here](https://learn.microsoft.com/en-us/visualstudio/liveshare/use/share-server-visual-studio-code#share-a-server).
1413
- To use PyCharm's Code With Me, first you can enable [Code With Me](https://www.jetbrains.com/help/pycharm/code-with-me.html), then set up [port forwarding](https://www.jetbrains.com/help/pycharm/code-with-me.html#port_forwarding).
1514

docs/user_guide/tutorials/02-collaboration/index.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,6 @@ First, let's create a GIS file and invite collaborators to the session.
3131
### Create Your GIS File
3232

3333
1. Open JupyterLab
34-
3534
- If you are using a local installation, start JupyterLab.
3635

3736
```

0 commit comments

Comments
 (0)