Skip to content

Add memory and web backends on Isar Community 3.2.1 - #1

Open
timcreatedit wants to merge 9 commits into
community-3.2.1from
feat/web-memory-backends
Open

Add memory and web backends on Isar Community 3.2.1#1
timcreatedit wants to merge 9 commits into
community-3.2.1from
feat/web-memory-backends

Conversation

@timcreatedit

@timcreatedit timcreatedit commented Aug 27, 2026

Copy link
Copy Markdown

Summary

  • base the Time Loop fork on the exact isar-community/isar-community 3.2.1 release, inheriting maintained fixes and Android 16 KB page-size support
  • add a shared pure-Dart engine and synchronous diskless IsarMemory helper for fast tests
  • add an IndexedDB backend for Flutter web using Dart JS interop
  • add backend capability handling and focused memory/browser conformance coverage

Stack boundary

This is the reusable fork layer. ClickUp can adopt the in-memory backend before taking any general ClickUp or Max web-target changes. The lower application adoption PR is time-loop/clickup_flutter#10323; app web support is stacked separately in #10296.

Base: time-loop/isar:community-3.2.1, which is the exact upstream isar-community/isar-community 3.2.1 release. The organization fork's v3 bookmark tracks the upstream community v3 tip.

Verification on the published tip

  • memory engine suite: 4 tests pass
  • Chrome IndexedDB suite: 6 tests pass, including persistence, rollback, deletion, compatible schema migration, owner exclusion, and watchers
  • package analyzer completes without errors (existing/style infos remain)

Notes

  • web remains async-only and rejects concurrent direct owners
  • filesystem, isolate, configured-size, and disk-migration behavior is capability-gated for the disposable memory backend
  • native core behavior is inherited from Isar Community 3.2.1; this PR's new runtime implementations are the pure-Dart memory and browser backends

…er 7.x

Based on tag 3.2.1 (first stable line with Android 16 KB page-size support
while staying on build ^2 / source_gen ^2, compatible with clickup_flutter's
codegen toolchain).

- Rename isar_community -> isar and isar_community_generator -> isar_generator
  (package names, directories, internal imports, build.yaml builder key) so
  that clickup_flutter's 293 'package:isar/isar.dart' imports keep working.
- Widen isar_generator's analyzer constraint from ^6.9.0 to '>=6.9.0 <8.0.0'.
  The 3.2.1 sources already use analyzer-7-compatible APIs; upstream only
  raises the constraint in 3.3.x, which requires build ^4 / source_gen ^4.
@upwind-code-us

upwind-code-us Bot commented Aug 27, 2026

Copy link
Copy Markdown

Upwind Upwind Code Scan - ✅ Proceed with Deployment

0 newly introduced vulnerabilities · 0 resolved · 0 total in this PR vs main

View full analysis in Upwind Console

Scan completed in 14s

Scan history (3 scans)
Commit Scanned at New Resolved Net
8e6f012 2026-08-27 08:46 UTC 0 0 0
378e009 2026-08-27 08:55 UTC 0 0 0
adc96e3 < 2026-08-27 11:47 UTC 0 0 0

Last scanned: adc96e3 · 2026-08-27 11:47 UTC

@upwind-code-us

upwind-code-us Bot commented Aug 27, 2026

Copy link
Copy Markdown

Upwind Upwind IaC Scan - ✅ Proceed with Deployment

0 misconfigurations detected

No default-branch baseline yet — showing all findings.

View full analysis in Upwind Console →

Scan completed in 3s

Scan history (3 scans)
Commit Scanned at New Resolved Net
8e6f012 2026-08-27 08:46 UTC 0 0 0
378e009 2026-08-27 08:55 UTC 0 0 0
adc96e3 < 2026-08-27 11:47 UTC 0 0 0

Last scanned: adc96e3 · 2026-08-27 11:47 UTC

@timcreatedit
timcreatedit force-pushed the feat/web-memory-backends branch from 8e6f012 to 378e009 Compare August 27, 2026 08:52
@timcreatedit
timcreatedit changed the base branch from v3 to community-3.2.1 August 27, 2026 08:53
@timcreatedit timcreatedit changed the title Add in-memory and web backends on isar-community v3 Add memory and web backends on Isar Community 3.2.1 Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant