Move ffi-table-provider example to ffi-library and correct doc building

Author: timsaucer

.github/workflows/test.yaml

@@ -91,7 +91,7 @@ jobs:
 
       - name: FFI unit tests
         run: |
-          cd examples/ffi-table-provider
+          cd examples/ffi-library
           uv run --no-project maturin develop --uv
           uv run --no-project pytest python/tests/_test_table_provider.py
 

docs/source/conf.py

@@ -71,6 +71,7 @@
 autoapi_member_order = "groupwise"
 suppress_warnings = ["autoapi.python_import_resolution"]
 autoapi_python_class_content = "both"
+autoapi_keep_files = False  # Set to True for debugging documentation generated
 
 
 def autoapi_skip_member_fn(app, what, name, obj, skip, options) -> bool:  # noqa: ARG001

docs/source/contributor-guide/ffi.rst

@@ -176,7 +176,7 @@ By convention the ``datafusion-python`` library expects a Python object that has
 ``TableProvider`` PyCapsule to have this capsule accessible by calling a function named
 ``__datafusion_table_provider__``. You can see a complete working example of how to
 share a ``TableProvider`` from one python library to DataFusion Python in the
-`repository examples folder <https://github.com/apache/datafusion-python/tree/main/examples/ffi-table-provider>`_.
+`repository examples folder <https://github.com/apache/datafusion-python/tree/main/examples/ffi-library>`_.
 
 This section has been written using ``TableProvider`` as an example. It is the first
 extension that has been written using this approach and the most thoroughly implemented.

examples/ffi-table-provider/.cargo/config.toml renamed to examples/ffi-library/.cargo/config.toml

@@ -16,7 +16,7 @@
 # under the License.
 
 [package]
-name = "ffi-table-provider"
+name = "ffi-library"
 version = "0.1.0"
 edition = "2021"