Repository navigation
feat(dashboard): show interests per synced profile - #376
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
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.
Summary
?profile=in the route).get_profile_interestsopens the database withopen_closedand reads without writing. Nothing is loaded into the resident brains.BlockedContenthides its unblock buttons when no handler is given.services::profile_interests::stored_interestscomputes from a brain value with the existingclassify_personaandtaste_profile.PersonaDetailsmoved there andget_flow_personauses it.stored_brainand is shared. FlowNeuro gets a read-onlystored_brain.Related issue
Flow-Tube/Flow#1034 (interests per synced profile, decrypted on the device only).
Change type
Validation
Run on the head of this branch (91dc5e2), in its worktree with the shared Cargo target dir:
pnpm test: 191 files, 1105 tests passedpnpm build: passedcargo fmt --manifest-path src-tauri/Cargo.toml --all -- --check: cleancargo clippy --manifest-path src-tauri/Cargo.toml --all-targets --all-features: finished; every warning it prints is on a line older than this stack (checked withgit blame)cargo test --manifest-path src-tauri/Cargo.toml --all-targets --all-features: 1118 passed, 0 failed, 9 ignoredNew tests:
services::profile_interests: a stored brain is shown as stored and left untouched; a profile without brains shows fresh ones and stores nothing.src/lib/linked/interestChoices.test.ts: which profiles the picker offers.Screenshots or recordings
Risk and compatibility
No migration. Reading another profile opens its database for a moment and closes it; nothing is written.
Another profile's view uses its stored brain as last saved, without the tidy-up the running profile applies when it loads.
No new secrets, private data, telemetry, or broad Tauri permissions were introduced.
User-facing documentation was updated where needed.
Dependency and lockfile changes are intentional and limited to this PR.
Breaking changes and upgrade steps are clearly documented.