The Immich API and database should store `null` instead of empty strings. Columns where this is happening: - [x] `album.description` (#30123) - [ ] `asset_exif.description` - [ ] `person.name` - [ ] `person.thumbnailPath` - [ ] `session.deviceType` - [ ] `session.deviceOS` - [x] `user.password` (#30223) - [ ] `user.profileImagePath` - [ ] `user.oauthId` - [ ] `user.name`
The Immich API and database should store
nullinstead of empty strings.Columns where this is happening:
album.description(feat: store null instead of empty string for album.description #30123)asset_exif.descriptionperson.nameperson.thumbnailPathsession.deviceTypesession.deviceOSuser.password(fix(server): store null instead of empty string for user password #30223)user.profileImagePathuser.oauthIduser.namefor everyone working on PRs for this issue, some hints :)
nulland''actually mean the same for that column''to null in the request schema to not break clients sending''+ add TODO comments to drop this in v4HistoryBuilderinfo on request fields indicating that clients must sendnullinstead of''in an upcoming major version''instead ofnullon the API surface to not break clients + add TODO comments to returnnullin v4HistoryBuilderinfo on response fields indicating that clients will sendnullinstead of''in an upcoming major version