NetHack VS openapi-generator

My configuration of Eglot is simple: (use-package eglot :hook (c-mode . eglot-ensure)). And it works for a single c file. But when I use this setup to read the code of NetHack, it doesn't work for linting and definition finding (M-.), even though eglot connection has no problem. I observed the same problems when reading the code of SQLite. Some specific problems I observed:

Since nethack 3.1.0, the source for nethack's "bestiary" has been dat/data.base, in plain text, processed into a file named "data" when building the program. The unprocessed file intended for the nethack's next version can be seen at https://github.com/NetHack/NetHack/blob/NetHack-3.7/dat/data.base (it's quite long).

Oh jeez, this fixes CVE-2023-24809 - i.e. nethack on shared systems may be risk due to buffer overflow in pre-3.6.7 versions.

I was looking at the list of diffs with some confusion about why it's such a small point release ( https://github.com/NetHack/NetHack/blob/NetHack-3.6/doc/fixe... ) before I re-read the release notes and saw the security issue.

For NetHack, part 1 comes up quite frequently because people like to port the game to new platforms / user interfaces, so there's a "windowport" system which exposes interfaces for gaining information about what the player can see – all the game's UI routines go through a small set of functions, which can be swapped out by recompiling the game (or you can even build NetHack as a library nowadays, so that you can link your own user interface against it). If you wanted to intercept part of the information about what the player could see, the easy way would be to modify an existing windowport to see that information and pass it to your interception tool (although this would require changing the game's source). If you were really set on not changing the source at all, you could probably use some sort of debugger API to intercept calls to the windowport, but changing the source is probably easier.

Tangentially related, this repo contains one of the greatest games ever made in C and once you have your feet wet would be very educational to look over.

Rogue, nethack, and Abuse come to mind, and then pretty much all the old id software stuff, along with the raven engine. These SDL tutorials might be of interest to you too, they are basically in the format of game sources with detailed explanations.

Congratulations! The dev team did something about your request. It's not what you wanted though.

EDIT: The relevant commit: https://github.com/NetHack/NetHack/commit/ef1eeed7550e38fa1e4ff0ef608f3c8b55eaa950

Of course you can compile the server from source if you have Go and the OpenAPI generator JAR (https://github.com/OpenAPITools/openapi-generator?tab=readme...)

Follow these steps : https://github.com/c100k/rebootx-on-prem/blob/master/.github...

And then :

(cd ./impl/http-server-go && GOARCH=amd64 GOOS=openbsd go build -o /app/rebootx-on-prem-http-server-go-openbsd-amd64 -v)

By adapting the arch if needed. Not tested, but it should work.

As an alternative, you can also use the official OpenAPI Generator, which is a more generic tool supporting a wide range of languages and frameworks.

I trialed generating SDKs using the OpenAPI Generator package, which was largely unsatisfactory.

If Swagger/OpenAPI is available, save yourself a lot of trouble and generate the client using OpenAPI Generator. If not, use a library like RestEase to make it significantly easier to create the client.

Then you can use oapi-codegen or openapi-generator to generate the Go (or other language) SDK for it.

Yep. For frontend use, I think https://www.npmjs.com/package/openapi-typescript is the most widely-used/well-regarded, though https://www.npmjs.com/package/orval seems to me to have some nicer features like react-query support.

There are other options too, I'd just stay away from "_the_ openapi generator" (https://openapi-generator.tech/) which does a pretty poor job IMO.

Disclaimer: I'm the founder of a company doing SDKs commercially, but we don't focus on the frontend right now, and our free plan is still in beta.

Now that I have a solid way to make an Open API spec and get a functioning mock server, I'd like to take it a step further and generate an SDK to call it. Many developers use SDKs to communicate with their backend services, and tools like OpenAPI Generator enable them to do so without having to manually build them. OpenAPI Generator will take an API spec and compile it down into an SDK in the language of your choice, including front-end compatible languages like typescript-fetch.

With the development of automatic code generation tools such OpenAPI generator (https://openapi-generator.tech/), the importance of API design rather than implementation is emphasized.

OpenAPI Generator (Free)

In short, OpenAPI Generator allows generation of API client librairies (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3).