Rebrand Diffly → Diffr (final Marketplace name)#3
Merged
Conversation
'Diffly' (name) was already taken on the Marketplace; 'Diffr' published successfully under publisher nimblesite. Rename the whole product to Diffr: id nimblesite.diffr, displayName Diffr, scheme/commands/symbols/ files all diffr, env DIFFR_E2E, OutputChannel Diffr. Provider file and icon assets renamed to match. 144 unit tests + lint + shipwright green.
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.
TLDR
Rename the entire extension from Diffly to Diffr — the final, Marketplace-accepted name (
nimblesite.diffr).Details
The Marketplace rejected
difflyas a name (already taken; public search did not surface it — only publish is authoritative).Diffrpublished successfully under publishernimblesite, so this PR makes the whole codebase consistent with that name.Mechanical, brand-wide rename (
Diffly/diffly/DIFFLY→Diffr/diffr/DIFFR) across 38 files:package.json):name→diffr,displayName→Diffr, all 11 command ids →diffr.*, all menu titles →Diffr: …, menu group prefix →diffr@N.SCHEME = "diffr",OUTPUT_CHANNEL_NAME = "Diffr",TITLE_PREFIX = "Diffr:", command/context/memento keys →diffr.*, URI helper symbols (buildDiffrUri,parseDiffrUri,DiffrUriComponents,DiffrAddressableRev, …), provider classDiffrContentProvider.src/providers/DifflyContentProvider.ts→DiffrContentProvider.ts;docs/assets/diffly-icon-*→diffr-icon-*.EXTENSION_ID = "nimblesite.diffr", scheme/URI assertions →diffr://…, E2E envDIFFR_E2E, proposed-api launch argnimblesite.diffr.release.ymlpackages/publishesdiffr-$VERSION.vsix;shipwright.jsonid/displayName → Diffr.No behavioural change — this is a pure rename. The
diffy://-style URI scheme value changes todiffr://, which only matters for in-session diff tabs (not persisted across the rename).How Do The Automated Tests Prove It Works?
menus.test.tsassertspackage.jsoncontributes.commands/menusare byte-equal to whatsrc/menus.tsgenerates from the renamedCOMMAND_IDS/TITLE_PREFIX, and that thecontribSourceControlHistoryItemMenuproposed API is still declared — proving everydiffr.*id andDiffr:title is internally consistent.uri.test.ts(68 assertions) round-tripsbuildDiffrUri/parseDiffrUrioverdiffr://commit/…anddiffr://index/…URIs incl. spaces, unicode,#/?, and rejects non-diffrschemes — proving the renamed scheme parses correctly.npm run lint,npm run shipwright:validate, andprettier --checkare clean;npm run buildreportspackage.json already in sync.Spec/Doc Changes
CLAUDE.md, docs/specs/spec.md, docs/plans/plan.md, docs/design-system.md, README.md, CHANGELOG.md all rebranded to Diffr.
Breaking Changes
Yes — the extension identity changes (
nimblesite.diffly→nimblesite.diffr) and command ids change (diffly.*→diffr.*). Pre-release only; no publisheddifflyusers exist.