Skip to content
Written with Claude
IMPORTANT

As you may notice, this page and pretty much the entire website were obviously created with the help of AI. I wonder how you could tell? Was it a big "Written With Claude" badge on every page? I moved it to the top now (with the help of AI of course) to make it even more obvious. There are a few blogposts that were written by me manually, the old-fashioned way, I hope there will be more in the future, and those have a similar "Human Written" badge. This project (not the website), on the other hand, is a very, very different story. It took me more than two years of painstaking and unpaid work in my own free time. A story that, hopefully, I will tell someday. But meanwhile, what would you like me to do? To create a complex documentation website with a bunch of highly technical articles with the help of AI and fake it, to give you an illusion that I also did that manually? Like the half of itnernet is doing at this point? How does that makes any sense? Is that even fair to you? Or maybe to create this website manually, the old-fashioned way, just for you? While working a paid job for a salary, most of you wouldn't even get up in the morning. Would you like me to sing you a song while we're at it? For your personal entertainment? Seriously, get a grip. Do you find this information less valuable because of the way this website was created? I give my best to fix it to keep the information as accurate as possible, and I think it is very accurate at this point. If you find some mistakes, inaccurancies or problems, there is a comment section at the bottom of every page, which I also made with the help of the AI. And I woould very much appreciate if you leave your feedback there. Look, I'm just a guy who likes SQL, that's all. If you don't approve of how this website was constructed and the use of AI tools, I suggest closing this page and never wever coming back. And good riddance. And I would ban your access if I could know how. Thank you for your attention to this matter.

HTTP File Options

Configuration for generating HTTP files for NpgsqlRest endpoints, compatible with REST Client extensions and Visual Studio HTTP file support.

Overview

json
{
  "NpgsqlRest": {
    "HttpFileOptions": {
      "Enabled": false,
      "Option": "File",
      "Name": null,
      "NamePattern": "{0}_{1}",
      "CommentHeader": "Simple",
      "CommentHeaderIncludeComments": true,
      "FileMode": "Schema",
      "FileOverwrite": true
    }
  }
}

Settings Reference

SettingTypeDefaultDescription
EnabledboolfalseEnable HTTP file generation.
Optionstring"File"Generation mode: "File", "Endpoint", or "Both".
NamestringnullBase file name. Uses database name if null, or "npgsqlrest" if no connection string.
NamePatternstring"{0}_{1}"File name pattern. {0} = database name, {1} = schema suffix (when FileMode is "Schema").
CommentHeaderstring"Simple"Comment header style: "None", "Simple", or "Full".
CommentHeaderIncludeCommentsbooltrueInclude routine comments in header (when CommentHeader is "Simple" or "Full").
FileModestring"Schema"File organization: "Database" or "Schema".
FileOverwritebooltrueOverwrite existing files.

Generation Options

OptionDescription
FileGenerate HTTP files in the file system.
EndpointGenerate endpoint(s) serving HTTP file content.
BothGenerate both file system files and endpoints.

Comment Header Styles

StyleDescription
NoneNo comment header above requests.
SimpleAdd routine name, parameters, and return values (default).
FullAdd entire routine code as comment header.

File Mode

ModeDescription
DatabaseCreate one HTTP file for the entire database.
SchemaCreate one HTTP file per schema.

HTTP Files

HTTP files (.http) are supported by:

These files allow you to send HTTP requests directly from your editor for API testing and documentation.

Example Configuration

Generate HTTP files per schema with full routine documentation:

json
{
  "NpgsqlRest": {
    "HttpFileOptions": {
      "Enabled": true,
      "Option": "File",
      "Name": "myapi",
      "NamePattern": "{0}_{1}",
      "CommentHeader": "Full",
      "CommentHeaderIncludeComments": true,
      "FileMode": "Schema",
      "FileOverwrite": true
    }
  }
}

Generate a single HTTP file for the entire database:

json
{
  "NpgsqlRest": {
    "HttpFileOptions": {
      "Enabled": true,
      "Option": "File",
      "FileMode": "Database",
      "CommentHeader": "Simple"
    }
  }
}

Serve HTTP files as endpoints:

json
{
  "NpgsqlRest": {
    "HttpFileOptions": {
      "Enabled": true,
      "Option": "Endpoint"
    }
  }
}

Next Steps

Comments

Released under the MIT License.