Skip to content

chore(rebrand): rename Constants.cs internals (NukeFileName, NukeDirectoryName, etc.)#60

Merged
ChrisonSimtian merged 1 commit into
mainfrom
chore/p3.5b-constants-internals
May 20, 2026
Merged

chore(rebrand): rename Constants.cs internals (NukeFileName, NukeDirectoryName, etc.)#60
ChrisonSimtian merged 1 commit into
mainfrom
chore/p3.5b-constants-internals

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Collaborator

Summary

Mechanical rename of five internal-only constants in Fallout.Build.Shared.Constants plus their call sites:

Old New
NukeFileName FalloutFileName
NukeDirectoryName FalloutDirectoryName
NukeCommonPackageId FalloutCommonPackageId
GetNukeDirectory(...) GetFalloutDirectory(...)
GlobalNukeDirectory GlobalFalloutDirectory

All five symbols are internalzero consumer-visible impact. Just leftover legacy naming.

14 files changed, 39 lines on each side. Refs #57.

Carve-outs preserved (deliberate)

  • LegacyNukeDirectoryName — back-compat constant whose value is the literal .nuke; renaming the symbol would be misleading.
  • UpstreamNukeRepository / UpstreamNukeRepositoryGit — pointers to nuke-build/nuke for legacy URL recognition.
  • NukeTelemetryVersion — MSBuild property in user-facing templates; deferred to the MSBuild-prop deprecation PR with the rest of that family.

Verification

  • dotnet build fallout.slnx -c Debug: 0 errors, 15 pre-existing warnings
  • dotnet test fallout.slnx: 391 passed, 7 skipped, 0 failed

Test plan

  • ubuntu-latest CI green
  • After merge, release run publishes 10.2.x with no behaviour change

🤖 Generated with Claude Code

…ctoryName, etc.) → Fallout*

Mechanical rename of the internal-only legacy constants in
Fallout.Build.Shared.Constants and their call sites:

  NukeFileName            → FalloutFileName
  NukeDirectoryName       → FalloutDirectoryName
  NukeCommonPackageId     → FalloutCommonPackageId
  GetNukeDirectory        → GetFalloutDirectory
  GlobalNukeDirectory     → GlobalFalloutDirectory

All five symbols are `internal` so this has no consumer-visible impact —
purely cleanup of leftover legacy naming. Refs #57.

## Carve-outs preserved (deliberate)

- `LegacyNukeDirectoryName` — back-compat constant whose VALUE is the
  literal `.nuke`, so renaming the symbol would be misleading.
- `UpstreamNukeRepository` / `UpstreamNukeRepositoryGit` — legacy
  recognition pointers to nuke-build/nuke.
- `NukeTelemetryVersion` — MSBuild property in user-facing templates;
  deferred to the MSBuild-prop deprecation PR.

## Verification

- dotnet build fallout.slnx -c Debug: 0 errors, 15 pre-existing warnings
- dotnet test fallout.slnx: 391 passed, 7 skipped, 0 failed

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian merged commit c23dd0b into main May 20, 2026
1 check passed
@ChrisonSimtian
ChrisonSimtian deleted the chore/p3.5b-constants-internals branch May 20, 2026 23:30
ChrisonSimtian added a commit that referenced this pull request May 22, 2026
CLAUDE.md no longer claimed the Nuke.* → Fallout.* structural rename
was pending — that landed in #54, #60, #65, #66 ages ago. Updates the
rebrand-status paragraph, the src/tests layout table, the production
project groupings (now including Fallout.Migrate and the vendored
Fallout.VisualStudio.SolutionPersistence), the tool-wrapper paths, and
fixes the CI-revival roadmap link from #7 (which is the CodeQL ticket)
to #8 (the actual CI-revival tracker).

README.md said releases publish to GitHub Packages — nuget.org has been
the primary feed since #58. Build-status table also had three URLs
hardcoded to ChrisonSimtian/nuke (the pre-rename slug). Also notes the
new docs-only paths-ignore on the release workflow.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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