mirror of
https://github.com/hanzoai/base.git
synced 2026-08-05 17:32:26 +00:00
hanzo-dev
951e13dbb5
Sweep the surviving auth-side tests so they no longer assert on
deleted constants / models / config knobs:
- collection / record exports + indexes / record-table-sync drop
the password column from auth-collection bootstrap fixtures and
the JSON snapshots
- TestRecordPublicExportAndMarshalJSON keeps the legacy "drop
password key from auth-record export" invariant (now enforced as
a hard-coded delete on the record_model.go side, not via the
field type) so accidental Set("password", x) calls never leak
- api-layer crud/auth-methods/collection-import scenarios drop the
"password / passwordConfirm / oldPassword / MFA / OTP" expected
keys and switch the auth-collection-create error fixtures to
email-validation + manager-access scenarios that still exist
- migrate-cmd / jsvm bind counts updated; jsvm $mails surface
drops to {verification, email-change}; PasswordField + the
sendRecordPasswordReset / sendRecordOTP / sendRecordAuthAlert
bindings removed from the type generator's expected fixture
- migrations/1747094400 raw-SQL implementation: the old delete
path went through the collection model (which can't rehydrate
pre-rip rows that still encode the deleted password field type)
and the system-collection guard. New approach: DROP TABLE IF
EXISTS + DELETE FROM _collections WHERE name=$x, then strip the
password entry from each surviving auth collection's JSON
fields array and ALTER TABLE DROP COLUMN. Idempotent on fresh
installs (no legacy table → no-op).
apis ./core ./plugins/jsvm ./forms all run green now.