gdtest-code-span-headings

A synthetic test package for code spans in docstring section headings.

Two functions with custom docstring section headings containing backtick code spans (e.g. ‘What Can Be Used in value=?’). Tests that title-casing preserves code verbatim and that slug generation strips backticks and special characters.

Source files

📁 gdtest_code_span_headings/

📄 __init__.py

"""Package with custom docstring section headings containing code spans."""

__version__ = "0.1.0"
__all__ = ["compare_values", "filter_range"]


def compare_values(data, column: str, value=None):
    """Compare column values against a threshold.

    Parameters
    ----------
    data
        The input data.
    column
        Column name to compare.
    value
        Comparison threshold. Accepts scalars, column references,
        or expressions.

    What Can Be Used in `value=`?
    -----------------------------
    The ``value=`` parameter accepts several types:

    - A scalar like ``10`` or ``"hello"``.
    - A column reference using ``col("other_col")``.
    - An expression using ``expr()``.

    Returns
    -------
    list
        Filtered results.
    """
    return []


def filter_range(data, column: str, left=None, right=None):
    """Filter values within a range.

    Parameters
    ----------
    data
        The input data.
    column
        Column name to filter.
    left
        Lower bound of the range.
    right
        Upper bound of the range.

    What Can Be Used in `left=` and `right=`?
    ------------------------------------------
    The ``left=`` and ``right=`` parameters accept:

    - Scalars (``int``, ``float``, ``str``).
    - Column references.
    - Expressions.

    Returns
    -------
    list
        Filtered results.
    """
    return []

📄 README.md

# gdtest-code-span-headings

A synthetic test package for code spans in docstring section headings.

📄 great-docs.yml generated

# Great Docs Configuration
# See https://posit-dev.github.io/great-docs/user-guide/configuration.html

# Module Name (optional)
# ----------------------
# Set this if your importable module name differs from the project name.
# Example: project 'py-yaml12' with module name 'yaml12'
# module: yaml12

# Docstring Parser
# ----------------
# The docstring format used in your package (numpy, google, or sphinx)
parser: numpy

# Dynamic Introspection
# ---------------------
# Use runtime introspection for more accurate documentation (default: true)
# Set to false if your package has cyclic alias issues (e.g., PyO3/Rust bindings)
dynamic: true

# API Discovery Settings
# ----------------------
# Exclude items from auto-documentation
# exclude:
#   - InternalClass
#   - helper_function

# Logo & Favicon
# ---------------
# Point to a single logo file (replaces the text title in the navbar):
# logo: assets/logo.svg
#
# For light/dark variants:
# logo:
#   light: assets/logo-light.svg
#   dark: assets/logo-dark.svg
#
# To show the text title alongside the logo, add: show_title: true

# Funding / Copyright Holder
# --------------------------
# Credit the organization that funds or holds copyright for this package.
# Displays in sidebar and footer. Homepage and ROR provide links.
# funding:
#   name: "Posit Software, PBC"
#   roles:
#     - Copyright holder
#     - funder
#   homepage: https://posit.co
#   ror: https://ror.org/03wc8by49

# API Reference Structure
# -----------------------
# Customize the sections below to organize your API documentation.
# - Reorder items within a section to change their display order
# - Move items between sections or create new sections
# - Use 'members: false' to exclude methods from documentation
# - Add 'desc:' to sections for descriptions

reference:
  - title: Functions
    desc: Utility functions
    contents:
      - compare_values
      - filter_range

# Site URL
# --------
# Canonical address of the deployed documentation site.
# Required for subdirectory deployments, skills page install commands,
# .well-known/ discovery, and sitemaps.
# site_url: "https://your-org.github.io/your-package/"

# Site Settings
# -------------
# site:
#   theme: flatly              # Quarto theme (default: flatly)
#   toc: true                  # Show table of contents (default: true)
#   toc-depth: 2               # TOC heading depth (default: 2)
#   toc-title: On this page    # TOC title (default: "On this page")

# Jupyter Kernel
# --------------
# Jupyter kernel to use for executing code cells in .qmd files.
# This is set at the project level so it applies to all pages, including
# auto-generated API reference pages. Can be overridden in individual .qmd
# file frontmatter if needed for special cases.
jupyter: python3

# CLI Documentation
# -----------------
# cli:
#   enabled: true              # Enable CLI documentation
#   module: my_package.cli     # Module containing Click commands
#   name: cli                  # Name of the Click command object