Skip to content

Fix: add swagger route to generated README for cs scaffold #7335

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix: add swagger route to generated README for cs scaffold #7335

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion packages/http-server-csharp/docs/usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ Models are partial, so you can add additional members for internal usage as need

After successful generation, you should:

- Use the SwaggerUI endpoint to test out the running service
- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
- Implement the business logic interfaces for your operations
- Update MockRegistration.cs, or register each of your interfaces as part of application startup
- Update configuration to suit your needs
6 changes: 3 additions & 3 deletions packages/http-server-csharp/src/lib/doc.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ title: Next Steps

# Next Steps

- Use the SwaggerUI endpoint to test out the running service
- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
- Implement business logic interfaces for your operations
- Register each of your implementations as part of application startup
- Update development and production configuration to suit your needs
Expand Down Expand Up @@ -134,7 +134,7 @@ Models are partial, so you can add additional members for internal usage as need

After successful generation, you should:

- Use the SwaggerUI endpoint to test out the running service
- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
- Implement the business logic interfaces for your operations
- Update MockRegistration.cs, or register each of your interfaces as part of application startup
- Update configuration to suit your needs
Expand Down Expand Up @@ -235,7 +235,7 @@ title: Next Steps

# Next Steps

- Use the SwaggerUI endpoint to test out the running service
- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
- Update business logic mocks with real business logic
${mocks.flatMap((m) => ` - \`mocks/${m.className}.cs\``).join("\n")}
- Update \`mocks/MockRegistration.cs\` if you update the constructor of business logic implementations.
Expand Down
2 changes: 1 addition & 1 deletion website/src/content/docs/docs/emitters/servers/http-server-csharp/project.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ Models are partial, so you can add additional members for internal usage as need

After successful generation, you should:

- Use the SwaggerUI endpoint to test out the running service
- Use the SwaggerUI endpoint (`/swagger`) to test out the running service
- Implement the business logic interfaces for your operations
- Update MockRegistration.cs, or register each of your interfaces as part of application startup
- Update configuration to suit your needs
Loading