smolblog
taxilang
| smolblog | taxilang | |
|---|---|---|
| 2 | 3 | |
| 3 | 81 | |
| - | - | |
| 6.1 | 9.3 | |
| 13 days ago | 2 months ago | |
| PHP | Kotlin | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
smolblog
-
Show HN: Supermaven, the first code completion tool with 300k token context
Trying it now on my super-specific codebase, and it seems to be working for the most part. Well done! I was able to get started on a new feature, and it got about 80% there with my custom-built framework: https://github.com/smolblog/smolblog/pull/61/commits/869a2ea...
-
OpenAPI v4 Proposal
I'm trying to go in this direction with an API I'm building at the moment in PHP: https://github.com/smolblog/smolblog-core/tree/feature/api-b... It uses a combination of definition-in-code (also used to translate the endpoint classes to the outside framework), reflection, and PHP annotations to generate the OpenAPI spec which I'm loading into Swagger to do testing.
taxilang
-
Orbital – Dynamically unifying APIs and data with no glue code
Under the hood, the tags (and associated query language) are actually Taxi - an OSS meta-language and toolchain we build (and have shared previously).
-
Quickly modernizing SOAP APIs
Taxi is a relatively new entrant in the API space. It's goal is to let developers add simple, (but type-safe) tags into their APIs, so software can understand how different APIs relate to one another.
-
OpenAPI v4 Proposal
One of the gripes I have about OpenAPI is that it has a very low signal-to-noise ratio. It was bad in JSON, it's just as bad in YAML, with an added whitespace pedantry.
It's great to see a number of alternatives listed in this thread - there's much more active development in this space then I was aware of, and I hope that some of it gets upstreamed back into OpenAPI.
I'll shamelessly plug our tool in this space - Taxi (https://github.com/taxilang/taxilang), which has a dedicated DSL (not YAML) you can either use standalone, or embeddedd within OpenAPI.
I also happen to think that (for internal teams at least), generating clients on ${apiSpec} is a form of tight coupling, where producer and consumer become tied together. If you can avoid it, you should, as it allows producers and consumers to stay loosely coupled and evolve independetly without the gymnastics of avoiding breaking changes.
I've talked about this before, with proposed solutions.[0]
[0]https://orbitalhq.com/blog/2023-01-16-using-semantic-metadat...
What are some alternatives?
oatx - Generator-less JSONSchema types straight from OpenAPI spec
openapi-codegen - A tool for generating code base on an OpenAPI schema.
effect-http - Declarative HTTP API library for effect-ts
orbital - Orbital automates integration between data sources (APIs, Databases, Queues and Functions). BFF's, API Composition and ETL pipelines that adapt as your specs change.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
swag - Automatically generate RESTful API documentation with Swagger 2.0 for Go.
speakeasy - Speakeasy CLI - Enterprise developer experience for your API
datamodel-code-generator - Pydantic model and dataclasses.dataclass generator for easy conversion of JSON, OpenAPI, JSON Schema, and YAML data sources.
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
goa - 🌟 Goa: Elevate Go API development! 🚀 Streamlined design, automatic code generation, and seamless HTTP/gRPC support. ✨