mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-09-30 20:49:41 +02:00
Codeman maintainer
c50bb02e62
The tree endpoint has accepted `showHidden=true` since it was written; the panel hardcoded `showHidden=false`, so dot-prefixed entries were unreachable from the File Viewer and opening one meant guessing its path. Adds a `.*` toggle to the panel header. It re-fetches instead of re-rendering the cached tree (the filtering is server-side), preserves the expanded directories so toggling does not collapse the tree, and persists per-device to its own `codeman:fileBrowserShowHidden` key. That key is deliberately not part of the app-settings object, which `saveAppSettings()` rebuilds from the settings-modal DOM and would drop it on the next save. Default is OFF, so an untouched install behaves exactly as before. Closes #221 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Changesets
Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works
with multi-package repos, or single-package repos to help you version and publish your code. You can find
the full documentation for it in the repository.
What is a changeset?
A changeset is a piece of information about changes made in a branch or commit. It holds three bits of information:
- What packages need to be released
- What semver bump type each package should receive (major / minor / patch)
- A summary of the changes
How do I create a changeset?
Run npx changeset or create a .md file in this directory with the following format:
---
"codeman": patch
---
Description of changes
The frontmatter specifies which package(s) to bump and the bump type. The body is the changelog entry.