Skip to content

Retire .Core from the published package ID #72

Description

@matt-edmondson

Keybinding.Core.csproj publishes as ktsu.Keybinding.Core. It should publish as ktsu.Keybinding.

Whether a repo splits its library into a .Core project is an internal decision about whether it
also ships an executable. Because the package ID mirrors the project name, that decision is
published. Forty-odd single-library repos in the org publish under the bare family name, so
consumers write ktsu.Extensions and ktsu.Containers but ktsu.Keybinding.Core here.

This one is live on nuget.org, so it is genuinely breaking rather than free.

Current package ID ktsu.Keybinding.Core
Versions published 35, latest 1.0.31
Target ktsu.Keybinding

Convention

A repo's principal package is ktsu.<Family>, where <Family> is the repo name, the solution
filename, and the leading segment of every package in the repo. The project filename is the package
ID minus ktsu.. Assembly name and root namespace equal the package ID.

Change

  1. Rename Keybinding.Core to Keybinding (folder, .csproj, and the solution entry).
  2. Ship ktsu.Keybinding at the next major.
  3. Republish ktsu.Keybinding.Core once as a deprecated meta-package that depends on ktsu.Keybinding, so pinned
    consumers get a working upgrade path rather than a dead ID.

Keybinding.Demo already matches the convention and needs no change.

If not now

Defer indefinitely if consumer churn outweighs the consistency. Nothing else in the audit depends
on this step. The rest of the naming work in this repo is free and can land without it.


Part of the estate-wide naming audit tracked in ktsu-dev/Sdk#36.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions