Server config restructuring

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
backend

Research direction

Start at the Server class and identify where its separate arguments are defined and passed. Trace the existing server setup before deciding how the configuration should be grouped; done means the server uses a config object at the class level and its existing setup remains covered.

Written by the indexing model from the issue text.

Description

The server ATM takes a set of separate arguments. This could get combined into a config object at Server class level.

Dominant language
TypeScript
Stars
4
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

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 push-based/angular-toolkit-mcp

All issues in push-based/angular-toolkit-mcp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.