fix(oc-capability): uses correct room field types#16781
fix(oc-capability): uses correct room field types#16781alperozturk96 wants to merge 3 commits intomasterfrom
Conversation
|
APK file: https://github.com/nextcloud/android/actions/runs/23749644834/artifacts/6180479612 |
efc5183 to
558ed56
Compare
|
APK file: https://github.com/nextcloud/android/actions/runs/24122694656/artifacts/6322219923 |
|
/backport to stable-33.1.0 |
Signed-off-by: alperozturk96 <alper_ozturk@proton.me> # Conflicts: # app/schemas/com.nextcloud.client.database.NextcloudDatabase/99.json # app/src/main/java/com/nextcloud/client/database/NextcloudDatabase.kt
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
Signed-off-by: alperozturk96 <alper_ozturk@proton.me>
558ed56 to
bb4c135
Compare
|
APK file: https://github.com/nextcloud/android/actions/runs/24388735581/artifacts/6423422154 |
|
blue-Light-Screenshot test failed, but no output was generated. Maybe a preliminary stage failed. |
Fixes
forbiddenFileNameCharacters, forbiddenFileNames, forbiddenFileNameExtensions, forbiddenFilenameBaseNamesThis PR fixes an inconsistency where several capabilities columns were defined as
INTEGERinRoombut actually storedJSONStringvalues.Why it previously worked
Data was read via cursor (getString), bypassing Room’s type mapping
Changes
Updated affected fields in
CapabilityEntityfromInt?toString?Added a migration that drops the capabilities table to ensure a clean schema
Adds capability dao and mapping between entity and
OCCapability