No description
The previous fix used db.insert() which serializes the extra field to JSON. However, the read functions (get_ticket, get_tickets, etc.) use fetchone/fetchall without a model parameter, so the extra field comes back as a JSON string. Added _parse_ticket_row() helper that: - Converts empty strings to None for name/email (existing logic) - Parses extra field from JSON string if needed (new) The isinstance(extra, str) check ensures compatibility with both: - SQLite: returns JSON as string - PostgreSQL/CockroachDB: may return native JSONB as dict 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .github/workflows | ||
| static | ||
| templates/events | ||
| tests | ||
| .gitignore | ||
| .prettierrc | ||
| __init__.py | ||
| API_DOCUMENTATION.md | ||
| config.json | ||
| crud.py | ||
| description.md | ||
| LICENSE | ||
| Makefile | ||
| manifest.json | ||
| migrations.py | ||
| models.py | ||
| package-lock.json | ||
| package.json | ||
| pyproject.toml | ||
| README.md | ||
| services.py | ||
| tasks.py | ||
| toc.md | ||
| uv.lock | ||
| views.py | ||
| views_api.py | ||
Events - LNbits extension
For more about LNBits extension check this tutorial
Sell tickets for events and use the built-in scanner for registering attendees
Events alows you to make tickets for an event. Each ticket is in the form of a unique QR code. After registering, and paying for ticket, the user gets a QR code to present at registration/entrance.
Events includes a shareable ticket scanner, which can be used to register attendees.





