swagger-typescript-api VS NetHack

RESTful APIs via swagger-typescript-api

TypeScript API generator via Swagger scheme

You said it yourself — the “official” generator is awful and very hard to modify or extend (well, you didn’t say that, but I’m saying it) and while there are many alternatives, they’re not always easy to find. I had some success with swagger-typescript-api[1], but eventually got tired of it and wrote my own generator. Despite looking around quite a bit at what’s available, I never heard of openapi-codegen, which looks quite good.

[1]: https://github.com/acacode/swagger-typescript-api

A lot of APIs nowadays have a Swagger / OpenAPI spec. You can autogenerate types from that using tools like swagger-typescript-api.

With such a contract your BE team should provide a https://swagger.io/tools/swagger-ui/ where the API definition can easily be viewed and tested. Also you can use generators to basically generate a boilerplate (types for all models, functions for all requests) for the entire API based on a contract: https://github.com/acacode/swagger-typescript-api This his already saved me months of work.. great tool.

If your backend is using Swagger, I'd highly recommend using the package swagger-typescript-api. It auto-generates your types and endpoints for you, based on a swagger.json file, which then simplifies where I store my API calls. The flexibility of this is that I can use these API calls in components, classes, Vuex, etc., and I'm not tied to something that I have to maintain as a UI dev.

If your backend is able to generate Swagger/OpenAPI JSON, you can use https://github.com/acacode/swagger-typescript-api to generate both TypeScript interfaces and an API client from the Swagger JSON.

download NetHack sources (https://github.com/NetHack/NetHack -> Code -> Download ZIP, unpack them on your computer)

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).

I am not really 100% sure what you are looking for. Are you looking for the actual picture? It is built during compilation from this uuencoded file https://github.com/NetHack/NetHack/blob/NetHack-3.7/win/win32/splash.uu

xNetHack is based on NetHack 3.7.0, and there was a bug (now fixed) in NetHack 3.7.0 that caused stair destinations to be messed up after a game is recovered. I wonder that has happened here: perhaps you are playing a version of xNetHack that inherited the bug from NetHack 3.7.0, this is a recovered game.

They won't be afraid of music in 3.7.

This is a bug that was fixed in the upcoming 3.7, in this commit. Basically, if the random filler created a space that was made inaccessible by the fixed level design getting overlaid on top of the random filler, a door could be created to make that space accessible.

There is not a comprehensive list of changes in existence. This one comes close but doesn't contain everything https://github.com/NetHack/NetHack/blob/NetHack-3.7/doc/fixes3-7-0.txt

I have an open github issue requesting that intrinsic invisibility be made only temporary, not permanent. That would make the invisibility mechanic more interesting since you could decide multiple times per game whether you want it, and extrinsic invisibility items would become more useful.