Consider not adding a CakeBuildLog as fallback to all loggers

Open
#326 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Quiet
Tech stack
csharp
Domain
build-system, tooling

Research direction

Start by locating the logger registration, the environment-variable check, and the CakeBuildLog fallback mentioned in the issue. Trace how those choices affect each log event, then establish whether registration can change during execution and define the expected behavior before adding focused coverage.

Written by the indexing model from the issue text.

Description

Is it real world use case that a build system logger is registered after checking the respective environment variable and that changes throughout execution?

Does it really need to be checked on every log event and have a CakeBuildLog fallback?

Dominant language
C#
Stars
33
Forks
18
Avg merge
3d 1h
Merged PRs (30d)
5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cake-contrib/Cake.BuildSystems.Module

All issues in cake-contrib/Cake.BuildSystems.Module

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.