Skip to content

Document ParameterService and BuildContext and move them to Fallout.Build.Execution - #707

Open
dennisdoomen wants to merge 1 commit into
Fallout-build:developfrom
dennisdoomen:engine/build-context-cleanup
Open

dennisdoomen wants to merge 1 commit into
Fallout-build:developfrom
dennisdoomen:engine/build-context-cleanup

Conversation

@dennisdoomen

Copy link
Copy Markdown
Collaborator

Follow-up to the move of ParameterService onto the BuildContext (FT-4, #309). Docs, namespace and dead-code cleanup only. No behavior change.

What changed

  • Rewrote the BuildContext docs in plain English. They now link docs/engine-de-statification.md for the plan.
  • Added docs to ParameterService. They explain the order of value sources and that each BuildContext owns one instance.
  • Moved both types to Fallout.Build.Execution. Both are internal, so there is no public API change. Consumers got a new using.
  • Removed ParameterService members that nothing calls:
    • IsParameter
    • GetParameterMemberName(string)
    • GetNamedArgument<T> overloads for Expression and MemberInfo
    • GetAllPositionalArguments<T>
    • four GetVariable<T> overloads
    • HasArgument

Notes for reviewers

  • Most other files in Fallout.Build still use Fallout.Common.* namespaces. This PR moves only the two types.
  • GitRepositoryWorktreeSpecs has 3 failing tests. They fail the same way on develop.

🤖 Generated with Claude Code

…uild.Execution

- Rewrite the BuildContext docs in plain English and link the de-statification plan.
- Document ParameterService and how each BuildContext owns one instance.
- Move both types from Fallout.Common(.Execution) to Fallout.Build.Execution.
- Remove ParameterService members that nothing calls.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@dennisdoomen
dennisdoomen requested a review from a team as a code owner October 10, 2026 10:33
@dennisdoomen dennisdoomen added target/vCurrent Targets the current version skip-changelog Dont add to the Github Release Notes labels Oct 10, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-changelog Dont add to the Github Release Notes target/vCurrent Targets the current version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant