What changed, and why it matters
This tiny commit reverts a database version bump and fixes a typo in a messaging refresh call. It appears to be a quick correction of an accidental change rather than a security fix. There is no clear security relevance visible in the code itself.
No security action required. Treat as a normal code-quality/revert commit. If the schemaVersion revert affects deployed app upgrades, verify that downgrade behavior does not corrupt existing user databases during migrations.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit makes two changes: (1) lowers the Drift shared database schemaVersion from 3 back to 2, suggesting a previous bump was committed by mistake; (2) renames a named parameter in a ShopInBit ticket-detail refresh call from forceMessages to forceUpdateMessages, matching the actual service method signature. Both look like ordinary bug/revert fixes with no direct security implications in the diff.
Changed components
lib/db/drift/shared_db/shared_database.dartlib/pages/shopinbit/shopinbit_ticket_detail.dartInspect captured patch +2 / −2
diff --git a/lib/db/drift/shared_db/shared_database.dart b/lib/db/drift/shared_db/shared_database.dart
index 83543b6..456b4f6 100644
--- a/lib/db/drift/shared_db/shared_database.dart
+++ b/lib/db/drift/shared_db/shared_database.dart
@@ -41,7 +41,7 @@ final class SharedDatabase extends _$SharedDatabase {
: super(executor ?? _openConnection());
@override
- int get schemaVersion => 3;
+ int get schemaVersion => 2;
@override
MigrationStrategy get migration => MigrationStrategy(
diff --git a/lib/pages/shopinbit/shopinbit_ticket_detail.dart b/lib/pages/shopinbit/shopinbit_ticket_detail.dart
index dfeb2d3..2a558ef 100644
--- a/lib/pages/shopinbit/shopinbit_ticket_detail.dart
+++ b/lib/pages/shopinbit/shopinbit_ticket_detail.dart
@@ -333,7 +333,7 @@ class _ShopInBitTicketDetailState extends ConsumerState<ShopInBitTicketDetail>
// so an ungated refresh would skip the fetch and the bubble's removal
// below would make the just-sent message vanish from the conversation.
try {
- await _shopinBitService.refreshOne(_id, forceMessages: true);
+ await _shopinBitService.refreshOne(_id, forceUpdateMessages: true);
} catch (_) {}
if (mounted) setState(() => _pending.remove(optimistic));
} else {
Why this scored 16/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.