Repository navigation
Keep account folders, note cards and focused checklist pages - #719
Open
michielbdejong wants to merge 3 commits into
Open
michielbdejong wants to merge 3 commits into
michielbdejong wants to merge 3 commits into
Conversation
michielbdejong
marked this pull request as ready for review
October 30, 2026 15:56
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Google Keep 0.2.0 uses a Google Keep folder containing the existing note resources. Google Keep View 0.3.0 renders the folder as cards and opens each card as its own checklist or text note, with unchecked items first and the actual completed count initially collapsed. Single-note loading fetches only that note and its linked items. Both installations are managed through Integrations, and view-only installation creates no Items table.
Existing note IDs, item IDs and sync baselines remain intact. Resource-page rendering has its own compatibility declarations and remains read-only; Open editing view retains the explicit table-grant flow. Provider-write settings are preserved. The new host pin also updates the experimental-store entry route and connection-consent test selectors.
Host dependency: ontola/atomic-server#2421, pinned at 7e98fa8577c55f3aa8f252689f97fbebecb608a7 by .atomic-server-ref. That host repairs interrupted migration grant bookkeeping and preserves pending in-frame grant continuations. Paired downstream profile alignment: https://github.com/ontola/atomic-saas/pull/250.
Validation at plugin head 4a6254b: 73 Keep sync unit tests, 31 view unit tests, relevant typechecks/tooling tests, published-module reproducibility and immutable-version checks, lint and formatting. Final native browser runs against the pinned host pass 29 tests across timesheets (6), issue-tracker (4), money (6), calendar (6), Keep view (5), full mock Keep sync (1), and pets (1), with one worker and zero retries. The host's apps/importer suite also passes 11/11. Synthetic desktop/mobile screenshots include folder-to-note navigation, 485 collapsed completed items and constrained layouts. The forced grant-acknowledgement race remains covered.
Exact-head CI passed all selected lanes and checks: https://github.com/ontola/atomic-plugins/actions/runs/41431917409. Catalog release, host deployment and live installation migration are waiting on the host and paired SaaS CI gates, queued for their self-hosted runner.