Skip to content

Change Oakton references to JasperFx #1551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeremydmiller merged 1 commit into from
Jul 10, 2025
Merged

Change Oakton references to JasperFx #1551

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/guide/diagnostics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ Wolverine can be configuration intensive, allows for quite a bit of customizatio
quite a bit of external infrastructure. All of those things can be problematic, so Wolverine tries to provide diagnostic tools
to unwind what's going on inside the application and the application's configuration.

Many of the diagnostics explained in this page are part of the [Oakton command line integration](https://jasperfx.github.io/oakton). As a reminder,
to utilize this command line integration, you need to apply Oakton as your command line parser as shown in the last line of the quickstart
Many of the diagnostics explained in this page are part of the [JasperFx command line integration](https://jasperfx.github.io/oakton) <== NOT SURE OF THE RIGHT URL. As a reminder,
to utilize this command line integration, you need to apply JasperFx as your command line parser as shown in the last line of the quickstart
sample `Program.cs` file:

<!-- snippet: sample_Quickstart_Program -->
Expand Down
Loading