a single-page result (max_pages < 2) suppressed the navigation row by dropping the whole view, which also discarded the consumer's custom per-page buttons. now: if the page carries custom buttons, keep the view and rebuild with update_buttons(nav=False) — nav items suppressed, custom buttons kept, and stop() NOT called so their callbacks still fire. a page with no custom buttons keeps the original drop-the-view behavior. verified by execution against real discord.py: single page + custom button -> start() -> callback FIRES on click (view kept, stop() not called); negative control on the old code drops the button entirely; the no-button single-page case is unregressed. Signed-off-by: disqualifier <dev@disqualifier.me>
16 lines
369 B
TOML
16 lines
369 B
TOML
[build-system]
|
|
requires = ["hatchling"]
|
|
build-backend = "hatchling.build"
|
|
|
|
[project]
|
|
name = "dpy_paginator"
|
|
version = "0.1.2"
|
|
description = "Button-navigated paginator for discord.py — config-free, injectable emojis, installable."
|
|
requires-python = ">=3.10"
|
|
dependencies = [
|
|
"discord.py>=2.0",
|
|
]
|
|
|
|
[tool.hatch.build.targets.wheel]
|
|
packages = ["src/dpy_paginator"]
|