mirror of
https://github.com/go-admin-team/go-admin.git
synced 2026-09-24 02:59:59 +00:00
zhangwenjian
d3e7f46a46
The list of stable packages named four packages of this repository, on the stated grounds that deduplicating app/demo's imports produces exactly those four. That reasoning was wrong in the one direction that matters: it sends a third-party author to depend on the host, and the host is a fork that every user edits. `go-admin` is also not a resolvable module path - it has no dot in its first element - so an application cannot require it at all without a replace directive, which is ignored outside the main module. Rewritten around what core promises instead, and around a different question: not "which packages does an application import" but "which conventions fail without saying anything". Those are now spelled out one by one, each with the mechanism that makes it silent - the response envelope the frontend reads by `code`, the tenant-scoped connection, `create_by` and the soft-delete marker, the data-scope middleware, the transaction shape, and the `apps/` prefix a packaged application's menu component must carry. Also states two things the document was missing: installing an application means trusting it with the host's database connection, at the same level of trust as importing any other Go package - there is no sandbox here and this does not pretend otherwise - and wiring an application in touches two places, not one, where missing the second means the migrations simply do not run, with no error. Claude-Session: https://claude.ai/code/session_01HPTAw8b8tAdFNFn8rKdPYx