Centralize notification prefix #38

Merged

barrettruth merged 1 commit from chore/standardize-notify-prefix into main

2026-05-05 15:31:38 +00:00

barrettruth commented

2026-05-05 15:29:09 +00:00

Owner

Problem

import-cost.nvim already uses the public package name in notifications, but the prefix is duplicated between normal logs and the migration warning.

Solution

Export one import-cost.util.prefix value and use it for both util.log() and the GitHub-source migration warning. This keeps the user-facing message unchanged while making the convention explicit.

Verification

nix develop .#ci --command just format
nix develop .#ci --command just lint
Headless Neovim migration warning capture confirmed the exact warning remains:
[import-cost.nvim]: Due to GitHub's historic unreliability, development has moved to Forgejo. See :help import-cost.nvim-migration to optionally update your plugin source configuration. This is a one-time warning.

## Problem `import-cost.nvim` already uses the public package name in notifications, but the prefix is duplicated between normal logs and the migration warning. ## Solution Export one `import-cost.util.prefix` value and use it for both `util.log()` and the GitHub-source migration warning. This keeps the user-facing message unchanged while making the convention explicit. ## Verification - `nix develop .#ci --command just format` - `nix develop .#ci --command just lint` - Headless Neovim migration warning capture confirmed the exact warning remains: `[import-cost.nvim]: Due to GitHub's historic unreliability, development has moved to Forgejo. See :help import-cost.nvim-migration to optionally update your plugin source configuration. This is a one-time warning.`

barrettruth added 1 commit

2026-05-05 15:29:09 +00:00

chore: centralize notification prefix

quality / Lint (pull_request) Successful in 5s

Details

quality / Format (pull_request) Successful in 8s

Details

dcfb95756d