Skip to content

Derive the plugin database requirement from plugin models - #1302

Merged
wu-clan merged 1 commit into
masterfrom
feature/plugin-database-config
Nov 10, 2026
Merged

wu-clan merged 1 commit into
masterfrom
feature/plugin-database-config

Conversation

@wu-clan

@wu-clan wu-clan commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

Remove the [plugin].database manifest field and derive the plugin database requirement from the plugin itself.

  • a plugin that defines ORM tables, or ships a sql/ directory, must provide the complete sql/postgresql/ script set
  • a plugin without tables and without a sql/ directory needs no database configuration at all

Validation:

ruff check --no-fix backend/plugin/validator.py backend/utils/dynamic_import.py
fba init

@wu-clan
wu-clan force-pushed the feature/plugin-database-config branch from a2ea854 to afa4d3c Compare November 10, 2026 05:50
@wu-clan
wu-clan force-pushed the feature/plugin-database-config branch from afa4d3c to b89309b Compare November 10, 2026 06:13
@wu-clan wu-clan changed the title Derive the plugin database requirement instead of declaring it Derive the plugin database requirement from plugin models Nov 10, 2026
@wu-clan
wu-clan merged commit b4cf726 into master Nov 10, 2026
3 checks passed
@wu-clan
wu-clan deleted the feature/plugin-database-config branch November 10, 2026 06:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant