fix: remove obsolete landlord profile indexes migration

This commit is contained in:
nessar committed 2026-08-17 14:18:15 +02:00
1 parent ecacab0b9f
commit b76dd27431
2 files changed
+1 -9

No files matched your search

+1
View File
@@ -70,6 +70,7 @@ Use the single-context documentation layout. See [domain.md](file:///home/nessar
- Define explicit input, output, API, and domain types.
- Prefer unions and enums over loosely related strings or multiple boolean flags.
- Use immutable transformations where practical.
- Do not use regular-expression `.test()` calls unless they are the only valid option and the user has explicitly authorized them; prefer more readable, maintainable validation alternatives.
- Avoid non-null assertions unless the invariant is guaranteed and clear.
- Validate data received from external APIs instead of trusting type assertions.
@@ -1,9 +0,0 @@
db.getSiblingDB('lmnp').landlords.createIndex(
{ oidcSubject: 1 },
{ name: 'landlords_oidc_subject_unique', unique: true, sparse: true },
);
db.getSiblingDB('lmnp').landlords.createIndex(
{ email: 1 },
{ name: 'landlords_email_unique', unique: true, sparse: true },
);