8000 feat(library): make the selected assets public, restricted or private at once by adeelahmad · Pull Request #629 · adeelahmad/lense · GitHub
[go: up one dir, main page]

Skip to content

feat(library): make the selected assets public, restricted or private at once - #629

Merged
adeelahmad merged 1 commit into
mainfrom
claude/project-thread-xfmkzn
Oct 18, 2026
Merged

adeelahmad merged 1 commit into
mainfrom
claude/project-thread-xfmkzn

Conversation

@adeelahmad
Copy link
8000 Copy Markdown
Owner

Requested by Adeel · project thread

Description

Before: an asset's visibility (public, restricted or private) could only be changed one asset at a time, from its own page.

After: owners select assets in the Library and pick Visibility › Public, Restricted or Private in the bulk bar. The toast's Undo puts each asset back to what it was, not to one shared value. Agents do the same with the existing POST /api/v1/metadata/bulk and set: {access}.

How: components/library/actions.ts remembers each asset's access before the change and sends the bulk metadata call; bulk-bar.tsx adds the Visibility menu for owners.

Motivation and Context

Item from the personal feature plan sheet ("share or hide many at once").

Screenshots (if appropriate):

n/a

Steps to reproduce (if appropriate):

Select assets in the Library, then Visibility › Private; press Undo on the toast.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change; ! in the title)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests (__tests__/library-catalogue.test.ts).
  • My change requires documentation updates, and I have updated docs/ accordingly (docs/access.md).
  • Users need more than the title to understand it, so I wrote it under ## Unreleased in CHANGELOG.md. Written as changelog.d/bulk-visibility.md, per build(release): changelog fragments in changelog.d/ instead of one Unreleased section #581.

Done questions (AGENTS.md)

  • Goal: delivers what the user wanted, merged on green CI.
  • Agents: usable through the API, MCP or an assistant tool. POST /api/v1/metadata/bulk with set: {access}, as documented.
  • Zero setup: no new prerequisite, .env edit or manual step.
  • Fewest clicks and keystrokes. Two clicks from a selection; Undo instead of a confirm dialog.
  • Configurable: new settings in the web app with defaults; wizard asks only what is required. n/a: no settings.
  • Light: default install still runs on a Raspberry Pi with cloud models.
  • Private and secure: data local and encrypted, passkeys, threat model updated. Only owners see the menu; the server checks ownership per asset as before.
  • Cost: cheapest path, model calls in the activity ledger, budgets respected. n/a: no model calls.
  • User decides: consequential or new actions wait for the user; defaults unchanged.
  • Upgrades: existing installs upgrade safely (upgrade step for stored-data changes). n/a: no stored-data change.
  • Honest: sources cited; labelled built, in progress or planned.
  • Tests, docs and generated files updated.
  • Open standards; dependencies keep Lens MIT. n/a: no dependencies.
  • Result reported with evidence; "refine later" items written down.
  • Reuse: existing Lens code and permissive libraries reused, nothing reinvented. Reuses the bulk metadata endpoint and its history.

Local CI (ci/local-ci.sh): pre-commit and PR title passed; Next.js passed except settings-kokoro.test.tsx, which was red on main until #621.


Generated by Claude Code

… at once

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QFUNzy1QZy5HhKAyJxTAYJ
@adeelahmad adeelahmad self-assigned this Oct 18, 2026
@adeelahmad
adeelahmad merged commit 0d3d1d4 into main Oct 18, 2026
10 checks passed
@adeelahmad
adeelahmad deleted the claude/project-thread-xfmkzn branch October 18, 2026 16:15
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.

2 participants

0