Request examples are not generated if serialize as V2.
app.UseSwagger(c => { c.SerializeAsV2 = true; });
It is working fine without this V2 settings.

According to https://api.sbanken.no/Bank/swagger/#!/GET/ApiV2TransactionsByCustomerIdByAccountNumberGet, transactionId is no longer available in API v2. It was available in v1 and the API response also contains the field.

Current API documentation:

Internbank.Api.Contracts.Core.Bank.Transactions.v2.Transaction {
	accountingDate (string, optional),
	interestDate (string, optional),
	ot

@ngraef
I'm adding an example response to one of my Get Routes like so:

@Response<string>(200, "Response example", "example String here")

However when debugging swaggerGen, I get the following message in the console:

  typescript-rest-swagger:metadata:methods Example extracted for ExportController.formattedDNA: undefined +0ms

I get the same message when I try using

Hello,

I've built the microservices using service fabric and they are currently deployed on my local cluster. I wanted to aggregrate the documentation and see the result. I installed swagger nuget package in the service layer and now I'm running your module. Here is how the json file looks like for me:

{

"list_url": [
    {

 "docs": "http://localhost:8622/swagger/docs/1.0,",

  "base_path"

DROP TABLE IF EXISTS users;
CREATE TABLE users (
user_id BIGINT PRIMARY KEY auto_increment,
username VARCHAR(128) UNIQUE,
password VARCHAR(256),
enabled BOOL,
);

after enabled BOOL，An extra comma

If the service no longer support a mime-type/data format, e.g. "application/json" or xml, it would be a breaking change for the users. There should be rules detecting these changes.