refactor: rename BaseSCIMClient in SCIMClient

Author: azmeuk

doc/changelog.rst

@@ -8,11 +8,11 @@ Changelog
 
     This version comes with breaking changes:
 
-    - :class:`~scim2_client.BaseSCIMClient` takes a mandatory :paramref:`~scim2_client.BaseSCIMClient.resource_types` parameter.
+    - :class:`~scim2_client.SCIMClient` takes a mandatory :paramref:`~scim2_client.SCIMClient.resource_types` parameter.
 
 Added
 ^^^^^
-- Implement :meth:`~scim2_client.BaseSCIMClient.register_naive_resource_types`.
+- Implement :meth:`~scim2_client.SCIMClient.register_naive_resource_types`.
 - Implement :meth:`~scim2_client.BaseSyncSCIMClient.discover` methods.
 
 [0.3.3] - 2024-11-29
@@ -28,9 +28,9 @@ Added
 
 Added
 ^^^^^
-- Implement :class:`~scim2_client.BaseSCIMClient` :paramref:`~scim2_client.BaseSCIMClient.check_request_payload`,
-  :paramref:`~scim2_client.BaseSCIMClient.check_response_payload` and
-  :paramref:`~scim2_client.BaseSCIMClient.raise_scim_errors` paramibutes,
+- Implement :class:`~scim2_client.SCIMClient` :paramref:`~scim2_client.SCIMClient.check_request_payload`,
+  :paramref:`~scim2_client.SCIMClient.check_response_payload` and
+  :paramref:`~scim2_client.SCIMClient.raise_scim_errors` paramibutes,
   to keep the same values for all the requests.
 
 [0.3.1] - 2024-11-29

doc/tutorial.rst

@@ -7,26 +7,29 @@ Initialization
 scim2-client depends on request engines such as `httpx <https://github.com/encode/httpx>`_ to perform network requests.
 This tutorial demonstrate how to use scim2-client with httpx, and suppose you have installed the `httpx` extra for example with ``pip install scim2-models[httpx]``.
 
-As a start you will need to instantiate a httpx :code:`Client` object that you can parameter as your will, and then pass it to a :class:`SCIM client <scim2_client.BaseSCIMClient>` object.
+As a start you will need to instantiate a httpx :code:`Client` object that you can parameter as your will, and then pass it to a :class:`~scim2_client.SCIMClient` object.
 In addition to your SCIM server root endpoint, you will probably want to provide some authorization headers through the httpx :code:`Client` :code:`headers` parameter:
 
 .. code-block:: python
 
     from httpx import Client
     from scim2_client.engines.httpx import SyncSCIMClient
 
-    client = Client(base_url="https://auth.example/scim/v2", headers={"Authorization": "Bearer foobar"})
+    client = Client(
+        base_url="https://auth.example/scim/v2",
+        headers={"Authorization": "Bearer foobar"},
+    )
     scim = SyncSCIMClient(client)
 
-You need to give to indicate to :class:`~scim2_client.BaseSCIMClient` all the different :class:`~scim2_models.Resource` models that you will need to manipulate, and the matching :class:`~scim2_models.ResourceType` objects to let the client know where to look for resources on the server.
+You need to give to indicate to :class:`~scim2_client.SCIMClient` all the different :class:`~scim2_models.Resource` models that you will need to manipulate, and the matching :class:`~scim2_models.ResourceType` objects to let the client know where to look for resources on the server.
 
 You can either provision those objects manually or automatically.
 
 Automatic provisioning
 ~~~~~~~~~~~~~~~~~~~~~~
 
 The easiest way is to let the client discover what :class:`~scim2_models.Schema` and :class:`~scim2_models.ResourceType` are available on the server by calling :meth:`~scim2_client.BaseSyncSCIMClient.discover`.
-It will dynamically generate models based on those schema, and make them available to use with :meth:`~scim2_client.BaseSCIMClient.get_resource_model`.
+It will dynamically generate models based on those schema, and make them available to use with :meth:`~scim2_client.SCIMClient.get_resource_model`.
 
 .. code-block:: python
     :caption: Dynamically discover models from the server
@@ -36,7 +39,7 @@ It will dynamically generate models based on those schema, and make them availab
 
 Manual provisioning
 ~~~~~~~~~~~~~~~~~~~
-To manually register models and resource types, you can simply use the :paramref:`~scim2_client.BaseSCIMClient.resource_models` and :paramref:`~scim2_client.BaseSCIMClient.resource_types` arguments.
+To manually register models and resource types, you can simply use the :paramref:`~scim2_client.SCIMClient.resource_models` and :paramref:`~scim2_client.SCIMClient.resource_types` arguments.
 
 
 .. code-block:: python
@@ -54,7 +57,7 @@ To manually register models and resource types, you can simply use the :paramref
    If you know that all the resources are hosted at regular server endpoints
    (for instance `/Users` for :class:`~scim2_models.User` etc.),
    you can skip passing the :class:`~scim2_models.ResourceType` objects by hand,
-   and simply call :meth:`~scim2_client.BaseSCIMClient.register_naive_resource_types`.
+   and simply call :meth:`~scim2_client.SCIMClient.register_naive_resource_types`.
 
     .. code-block:: python
         :caption: Manually registering models and resource types
@@ -99,20 +102,20 @@ Have a look at the :doc:`reference` to see usage examples and the exhaustive set
 Request and response validation
 ===============================
 
-By default, the data passed to the :class:`SCIM client <scim2_client.BaseSCIMClient>` as well as the server response will be validated against the SCIM specifications, and will raise an error if they don't respect them.
+By default, the data passed to the :class:`SCIM client <scim2_client.SCIMClient>` as well as the server response will be validated against the SCIM specifications, and will raise an error if they don't respect them.
 However sometimes you want to accept invalid inputs and outputs.
 To achieve this, all the methods provide the following parameters, all are :data:`True` by default:
 
-- :paramref:`~scim2_client.BaseSCIMClient.check_request_payload`:
+- :paramref:`~scim2_client.SCIMClient.check_request_payload`:
   If :data:`True` (the default) a :class:`~pydantic.ValidationError` will be raised if the input does not respect the SCIM standard.
   If :data:`False`, input is expected to be a :data:`dict` that will be passed as-is in the request.
-- :paramref:`~scim2_client.BaseSCIMClient.check_response_payload`:
+- :paramref:`~scim2_client.SCIMClient.check_response_payload`:
   If :data:`True` (the default) a :class:`~pydantic.ValidationError` will be raised if the server response does not respect the SCIM standard.
   If :data:`False` the server response is returned as-is.
 - :code:`expected_status_codes`: The list of expected status codes in the response.
   If :data:`None` any status code is accepted.
   If an unexpected status code is returned, a :class:`~scim2_client.errors.UnexpectedStatusCode` exception is raised.
-- :paramref:`~scim2_client.BaseSCIMClient.raise_scim_errors`: If :data:`True` (the default) and the server returned an :class:`~scim2_models.Error` object, a :class:`~scim2_client.SCIMResponseErrorObject` exception will be raised.
+- :paramref:`~scim2_client.SCIMClient.raise_scim_errors`: If :data:`True` (the default) and the server returned an :class:`~scim2_models.Error` object, a :class:`~scim2_client.SCIMResponseErrorObject` exception will be raised.
   If :data:`False` the error object is returned.
 
 
@@ -134,7 +137,7 @@ Currently those engines are shipped:
   It takes a WSGI app and directly execute the server code instead of performing real HTTP requests.
   This is faster in unit test suites, and helpful to catch the server exceptions.
 
-You can easily implement your own engine by inheriting from :class:`~scim2_client.BaseSCIMClient`.
+You can easily implement your own engine by inheriting from :class:`~scim2_client.SCIMClient`.
 
 Additional request parameters
 =============================

scim2_client/__init__.py

@@ -1,5 +1,5 @@
-from .client import BaseSCIMClient
 from .client import BaseSyncSCIMClient
+from .client import SCIMClient
 from .errors import RequestNetworkError
 from .errors import RequestPayloadValidationError
 from .errors import ResponsePayloadValidationError
@@ -12,7 +12,7 @@
 from .errors import UnexpectedStatusCode
 
 __all__ = [
-    "BaseSCIMClient",
+    "SCIMClient",
     "BaseSyncSCIMClient",
     "SCIMClientError",
     "SCIMRequestError",