nlweb-ai/nlweb-net

馃З Middleware: Response headers injection (scaffold)

Open

#86 opened on Aug 18, 2025

View on GitHub
聽(0 comments)聽(0 reactions)聽(0 assignees)C#聽(8 forks)auto 404
configurationgood first issuemiddleware

Repository metrics

Stars
聽(23 stars)
PR merge metrics
聽(PR metrics pending)

Description

Introduce a minimal response headers injection scaffold (incremental toward #39).

Scope

  • Create a ResponseHeadersOptions class under src/NLWebNet and wire minimal binding
  • Add a simple middleware or extend existing NLWebMiddleware to set one sample header when configured
  • Add an example to samples/Demo/appsettings.json

Acceptance Criteria

  • Running the demo sets at least one header from config

Labels: configuration, middleware, good first issue

Link: #39

Contributor guide

Research direction
Examine the existing NLWebMiddleware and NLWebNet namespace for similar patterns. Create a ResponseHeadersOptions class following the project's conventions. Wire it in the service registration. Add a sample header in the appsettings.json and verify via a breakpoint or HTTP response inspection.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git.NET 9C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80