Skip to content

Rename the application to DevNotes - #211

Merged
vmillet-dev merged 1 commit into
mainfrom
rename-to-devnotes
Sep 18, 2026
Merged

vmillet-dev merged 1 commit into
mainfrom
rename-to-devnotes

Conversation

@vmillet-dev

Copy link
Copy Markdown
Owner

DevBox was named for a Swiss-army-knife premise that no longer exists — the crypto and
formatter modules were removed once it became clear they would ship dead code. What ships
is a notes and snippets manager, and the name now says so.

What it cost, and what it did not

The displayed name was one line. [package.metadata.devnotes] display-name reaches
DEVNOTES_DISPLAY_NAMEAPP_METADATA.nameAPP_INFO.name → the 22 translated
strings per locale that write {{app}}. No translated string spells the name out, and
transloco-loader.spec.ts still holds that.

Three things escaped that channel and were renamed by hand: the OS window title in
tauri.conf.json, the sample tag (notes.samples.tags.devnotes — the guard compares
against APP_INFO.name and is case-sensitive, so a lowercase devbox slipped past it),
and the assertions in six spec files.

The four names that are a library's address

before after
Tauri identifier com.devbox.app com.devnotes.app
db::DB_FILE_NAME devbox.sqlite3 (+ -wal, -shm) devnotes.sqlite3
Preference prefix devbox.<key> devnotes.<key>
Export extension .devbox .devnotes

app_data_dir() is data_dir()/identifier, so these four decide where every library
lives. Moving them normally needs a startup migration that adopts the old directory —
without one, an installed copy opens on a virgin profile with the notes still on disk and
no way in, since the key file is what opens the database.

They moved anyway, and deliberately: the application has no users yet. The ⚠️ in
CLAUDE.md now records the constraint rather than the exemption, so the next rename
cannot be done with a sed.

Verified

cargo check · clippy -D warnings · fmt --check · cargo test (486) ·
npm test (1354) · npm run test:scripts (34) · npm run lint · npm run build ·
npm run bindings (regenerated, no drift).

npm run test:e2e: 21/21 spec files, against the assembled binary carrying the new
identifier. com.devnotes.app.e2e was created from nothing and 01-first-launch met the
virgin profile it expects — which is the only proof that the identifier rename works end
to end.

One thing this PR cannot do

The updater endpoint now points at github.com/vmillet-dev/devnotes-rs. The repository
has to be renamed before the next release
, or the manifest resolves to nothing. GitHub
keeps the old → new redirect, so the releases already out keep updating.

The displayed name comes from `[package.metadata.devnotes] display-name`
and reaches every translated string through `{{app}}` on its own; the
crate, the binary, the Angular project and the repository slug follow it.

The four names that make up a library's address — the Tauri identifier,
`devnotes.sqlite3`, the `devnotes.` preference prefix and the `.devnotes`
export extension — moved with it rather than waiting for a startup
migration, since nothing is installed anywhere yet.
@vmillet-dev vmillet-dev added this to the v0.3.1 — Room to work milestone Sep 18, 2026
@vmillet-dev
vmillet-dev merged commit ae42f54 into main Sep 18, 2026
11 checks passed
@vmillet-dev
vmillet-dev deleted the rename-to-devnotes branch September 18, 2026 14:23
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