hosaka

@hosaka@programming.dev
0 Post – 8 Comments
Joined 1 years ago

openpgp4fpr:2a420f2982e589326ca49d1b0644b87ed144c988

It's a reader assistance, some paid for tool that highlights parts of a word, can't recall what it's called...

10 more...

I think it's is not aimed to protect against potential attacks, this is aimed at a developer using/writing modules of code. This is not a security guard

Use Open API schema. You can define data models and endpoints or just the models, I do this at work. Then generate your code using openapi-generator.

11 more...

Did exactly this recently and it's been quite good. Forgejo-runner was a bit tricky to setup but overall a great experience.

2 more...

Honestly not sure about Swagger, I've only ever used swagger-ui to show the API docs on a webpage. OpenAPI as a standard and openapi-generator are not abandoned and quite active. I'll give you an example of how I use it.

I have a FastAPI server in python that defines some endpoints and data models that it can work with, it exports an openapi.json definition. I also have a common schemas library defined with pydantic that also exports an openapi.json (python was chosen to make it easier for other team members to make quick changes). This schemas library is also imported in the FastAPI app, basically only the data models are shared.

I use the FastAPI/openapi.json to generate C++ code in one application (the end user app) using the openapi-generator-cli, serialize/deserialize is handled by the generated code, since the pydantic schema is a dependency of the FastAPI server, both the endpoints and data models get generated. The pydantic/openapi.json is also used by our frontend written in typescript to generate data models only since the frontend doesn't need to call FastAPI directly but it has an option to in the future by generating from FastAPI/openapi.json instead.

This ensures that we're using the same schema across all codebases. When I make changes to the schema, the code gets re-generated and included in the new c++/web app builds. There's multiple ways to go about versioning, but for data only schema I'd just keep it backwards compatible forever (by adding new props as optional field rather than required and slowly deprecating/removing props that are no longer used).

I found this to be more convoluted than just using something like gRPC/Protobuf (which can also be serialized from JSON), I've used it before and it was great. But for other devs that need to change a few lines of python and not having to deal with protobuf compiler, it's a more frictionless solution at the cost of more moving parts and some CICD setup on my side.

HTMX is great by I don't think it's what OP needs since the input and desired output is not hypermedia in the first place.

1 more...

Yeah it's a ci/cd runner, using a tool called "act". I self-host forgejo and the runner is a docker-in-docker container, but one could set it up with the public forgejo as well. It's pretty neat!

If only it wasn't paywalled