Deal with Config Better

Open
#6 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp

Research direction

The issue mentions configuration and an output folder but names no files, tests, or entry points. Start by locating where configuration is read or copied, then clarify the intended workflow with the maintainer. Done should remove the need for users to manually change or copy configuration into the output folder.

Written by the indexing model from the issue text.

Description

Currently user has to know to change/copy config to output folder. This is a poor solution.

Dominant language
C#
Stars
2
Forks
1
PR merge metrics
No merged PRs in 30d

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 cschladetsch/CppIncode

All issues in cschladetsch/CppIncode

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.