Skip to content

Commit f873ff4

Browse files
chore: prepare package metadata and documentation for v1.6.0
Prepare the project for the upcoming v1.6.0 release.
2 parents 1915ba2 + 94a97b2 commit f873ff4

3 files changed

Lines changed: 42 additions & 6 deletions

File tree

DebugProbe.AspNetCore/DebugProbe.AspNetCore.csproj

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,18 +8,22 @@
88
<NoWarn>1591</NoWarn>
99

1010
<PackageId>DebugProbe.AspNetCore</PackageId>
11-
<Version>1.5.0</Version>
11+
<Version>1.6.0</Version>
1212

1313
<Authors>Georgi Hristov</Authors>
1414

15-
<Description>Inspect and debug HTTP requests and responses directly inside ASP.NET Core applications.</Description>
15+
<Description>Inspect HTTP traffic and compare request/response traces across ASP.NET Core environments.</Description>
1616

17-
<PackageTags>aspnetcore;debugging;http;middleware;diagnostics;tracing;observability;api-debugging;developer-tools</PackageTags>
17+
<PackageTags>aspnetcore;debugging;http;middleware;diagnostics;tracing;observability;api-debugging;developer-tools;trace-comparison;environment-comparison</PackageTags>
18+
19+
<PackageReleaseNotes>
20+
Adds trace comparison across environments, improved DebugProbe dashboard workflows, and support for comparing request and response differences between captured API runs.
21+
</PackageReleaseNotes>
1822

1923
<PackageIcon>icon.png</PackageIcon>
2024
<PackageReadmeFile>README.md</PackageReadmeFile>
2125

22-
<RepositoryUrl>https://github.com/georgidhristov/DebugProbe.AspNetCore</RepositoryUrl>
26+
<RepositoryUrl>https://github.com/DebugProbe/DebugProbe.AspNetCore</RepositoryUrl>
2327
<RepositoryType>git</RepositoryType>
2428

2529
<PackageProjectUrl>https://debugprobe.dev</PackageProjectUrl>

DebugProbe.AspNetCore/README.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,13 @@
22

33
DebugProbe.AspNetCore is a lightweight ASP.NET Core debugging tool for inspecting HTTP traffic directly inside your application.
44

5-
It captures request and response data, exposes a local dashboard, and helps compare traces during API development without requiring a proxy, browser extension, or external SaaS service.
5+
It captures request and response data, exposes a local dashboard, and helps compare traces across environments so you can spot differences between local, staging, and other API runs.
66

77
## Links
88

99
- Website: [debugprobe.dev](https://debugprobe.dev)
1010
- Documentation: [debugprobe.dev/docs](https://debugprobe.dev/docs)
11+
- Roadmap: [Roadmap.md](https://github.com/DebugProbe/DebugProbe.AspNetCore/blob/main/Roadmap.md)
1112
- Live demo: [demo.debugprobe.dev/debug](https://demo.debugprobe.dev/debug)
1213
- Demo API: [demo.debugprobe.dev/swagger](https://demo.debugprobe.dev/swagger)
1314
- NuGet: [DebugProbe.AspNetCore](https://www.nuget.org/packages/DebugProbe.AspNetCore)
@@ -67,6 +68,21 @@ app.UseDebugProbe();
6768
- Sensitive header masking
6869
- Outgoing `HttpClient` request tracing
6970

71+
## Trace Compare
72+
73+
DebugProbe can compare a local trace with a trace captured by another DebugProbe-enabled application.
74+
75+
Typical workflow:
76+
77+
1. Run both applications with DebugProbe enabled.
78+
2. Open the local dashboard at `/debug`.
79+
3. Open the trace you want to compare.
80+
4. Use the compare action and provide the remote application's base URL and trace ID.
81+
82+
Compare is useful when checking differences between local and remote environments, repeated runs, or two versions of the same API flow.
83+
84+
Dynamic values such as IDs, timestamps, tokens, and selected headers are normalized so the compare view focuses on meaningful request and response differences.
85+
7086
## Security Defaults
7187

7288
DebugProbe masks common sensitive headers automatically:

README.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,13 @@
22

33
DebugProbe.AspNetCore is a lightweight ASP.NET Core debugging tool for inspecting HTTP traffic directly inside your application.
44

5-
It captures request and response data, exposes a local dashboard, and helps compare traces during API development without requiring a proxy, browser extension, or external SaaS service.
5+
It captures request and response data, exposes a local dashboard, and helps compare traces across environments so you can spot differences between local, staging, and other API runs.
66

77
## Links
88

99
- Website: [debugprobe.dev](https://debugprobe.dev)
1010
- Documentation: [debugprobe.dev/docs](https://debugprobe.dev/docs)
11+
- Roadmap: [Roadmap.md](https://github.com/DebugProbe/DebugProbe.AspNetCore/blob/main/Roadmap.md)
1112
- Live demo: [demo.debugprobe.dev/debug](https://demo.debugprobe.dev/debug)
1213
- Demo API: [demo.debugprobe.dev/swagger](https://demo.debugprobe.dev/swagger)
1314
- NuGet: [DebugProbe.AspNetCore](https://www.nuget.org/packages/DebugProbe.AspNetCore)
@@ -67,6 +68,21 @@ app.UseDebugProbe();
6768
- Sensitive header masking
6869
- Outgoing `HttpClient` request tracing
6970

71+
## Trace Compare
72+
73+
DebugProbe can compare a local trace with a trace captured by another DebugProbe-enabled application.
74+
75+
Typical workflow:
76+
77+
1. Run both applications with DebugProbe enabled.
78+
2. Open the local dashboard at `/debug`.
79+
3. Open the trace you want to compare.
80+
4. Use the compare action and provide the remote application's base URL and trace ID.
81+
82+
Compare is useful when checking differences between local and remote environments, repeated runs, or two versions of the same API flow.
83+
84+
Dynamic values such as IDs, timestamps, tokens, and selected headers are normalized so the compare view focuses on meaningful request and response differences.
85+
7086
## Security Defaults
7187

7288
DebugProbe masks common sensitive headers automatically:

0 commit comments

Comments
 (0)