Skip to content

Commit fd3003a

Browse files
chore: introduce typo checker to pre-commit and fix typos (#686)
1 parent 2d7baea commit fd3003a

27 files changed

+87
-76
lines changed

.pre-commit-config.yaml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
exclude: (quetz/migrations)
12
repos:
23
- repo: https://github.com/pycqa/isort
34
rev: 5.12.0
@@ -41,3 +42,8 @@ repos:
4142
rev: v1.1.314
4243
hooks:
4344
- id: pyright
45+
- repo: https://github.com/Quantco/pre-commit-mirrors-typos
46+
rev: 1.16.26
47+
hooks:
48+
- id: typos-conda
49+
exclude: (quetz/tests/authentification/test_oauth.py)

_typos.toml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
[default.extend-words]
2+
fo = "fo"
3+
4+
[files]
5+
extend-exclude = ["quetz/migrations/*.po", "quetz/tests/authentification/test_oauth.py"]

docker/jupyterhub_config.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1161,7 +1161,7 @@
11611161
#
11621162
# This function is called after the user has passed all authentication checks
11631163
# and is ready to successfully authenticate. This function must return the
1164-
# authentication dict reguardless of changes to it.
1164+
# authentication dict regardless of changes to it.
11651165
#
11661166
# This maybe a coroutine.
11671167
#

docs/source/deploying/authenticators.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ For example, the custom authenticator might be:
9898
Registering authenticator
9999
^^^^^^^^^^^^^^^^^^^^^^^^^
100100

101-
The standard way to register an authenticator with Quetz, is to distibute it as a plugin
101+
The standard way to register an authenticator with Quetz, is to distribute it as a plugin
102102
(see :ref:`plugins_section`).
103103
To automatize the creation of a plugin, check out our cookiecutter `template`_.
104104

docs/source/deploying/configuration.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -72,14 +72,14 @@ Configure default user permissions, creating default channel and super-admin per
7272
admins = ["github:admin_user"]
7373
# users with maintainer role
7474
maintainers = ["google:other_user"]
75-
# users with memeber role
75+
# users with member role
7676
members = ["github:some", "github:random", "github:name"]
7777
# default role assigned to new users
7878
# leave out if role should be null
7979
default_role = "member"
8080
# create a default channel for new users named {username}
8181
create_default_channel = false
82-
# wether to collect email addresses when users register
82+
# whether to collect email addresses when users register
8383
collect_emails = false
8484
8585
You can use one of the following options to configure privileged users:
@@ -193,7 +193,7 @@ Quetz can store packages in Google Cloud Storage. To configure, use the followin
193193
region="..."
194194
195195
:project: The Google Cloud Project ID to work under
196-
:token: A token to pass the `gcsfs`. See the `gcsfs documention <https://gcsfs.readthedocs.io/en/latest/index.html#credentials>`_ for valid values.
196+
:token: A token to pass the `gcsfs`. See the `gcsfs documentation <https://gcsfs.readthedocs.io/en/latest/index.html#credentials>`_ for valid values.
197197
:bucket_prefix:
198198
:bucket_suffix: channel buckets on GCS are created with the following semantics: ``{bucket_prefix}{channel_name}{bucket_suffix}``
199199
:cache_timeout: Timeout in s after which local GCS cache entries are invalidated. Set to a value <=0 to disable caching completely. Default is that entries are never invalidated.
@@ -270,9 +270,9 @@ You can also use a couple of environment variables to configure the behaviour of
270270
Variable description values default
271271
======================= ====================================== =========================== ===================
272272
``QUETZ_LOG_LEVEL`` log level ERROR, INFO, WARNING, DEBUG INFO or config file
273-
``QUETZ_API_KEY`` api key used by quetz-client log level string
273+
``QUETZ_API_KEY`` api key used by quetz-client string
274274
``QUETZ_TEST_DATABASE`` uri to the database used in tests string sqlite:///:memory:
275-
``QUETZ_TEST_DBINIT`` method to create db tabels in tests "create-tables" or "create-tables"
275+
``QUETZ_TEST_DBINIT`` method to create db tables in tests "create-tables" or "create-tables"
276276
"use-migrations"
277277
``S3_ACCESS_KEY`` access key to s3 (used in tests) string
278278
``S3_SECRET_KEY`` secret key to s3 (used in tests) string

docs/source/deploying/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ Deploying
22
=========
33

44
There are many options for deploying a package repository with Quetz. You can deploy Quetz either locally for
5-
testing, on a production server or in the cloud. The process can be tailored to your needs and exisiting
5+
testing, on a production server or in the cloud. The process can be tailored to your needs and existing
66
infrastructure.
77

88
.. toctree::

docs/source/deploying/migrations.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ When the data classes in Quetz are modified (for example, a column is added, rem
55

66
.. note::
77

8-
Before running any of the commands below, you need to make sure that your database is backed up. The backup process depends on the infrastrcuture, but in the simplest case it may involve the dump of the whole database (using ``pg_dump`` for example).
8+
Before running any of the commands below, you need to make sure that your database is backed up. The backup process depends on the infrastructure, but in the simplest case it may involve the dump of the whole database (using ``pg_dump`` for example).
99

1010
Migrating database
1111
------------------

docs/source/qeps/qep-001-user-permissions.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ Roles can be configure with a config file:
6161
admins = ["wolfv"]
6262
# users with maintainer role
6363
maintainers = ["btel"]
64-
# users with memeber role
64+
# users with member role
6565
members = ["some", "random", "name"]
6666
# default role assigned to new users
6767
# leave out if role should be null

quetz/authentication/azuread.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ class AzureADAuthenticator(OAuthAuthenticator):
1616
tenant_id = "tenant-name or id"
1717
1818
You can obtain ``client_id`` and ``client_secret`` by registering your
19-
application with AzureAD platfrom at this URL:
19+
application with AzureAD platform at this URL:
2020
`https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/RegisteredApps`
2121
2222
The ``tenant_id`` can either be a specific tenant's GUID identifier or one of three

quetz/authentication/google.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ class GoogleAuthenticator(OAuthAuthenticator):
1818
client_secret = "03728444a12abff17e9444fd231b4379d58f0b"
1919
2020
You can obtain ``client_id`` and ``client_secret`` by registering your
21-
application with Google platfrom at this URL:
21+
application with Google platform at this URL:
2222
`<https://console.developers.google.com/apis/credentials>`_.
2323
"""
2424

0 commit comments

Comments
 (0)