emykhailenko

thanks ;)

I recently noticed how much code is spent simply producing an enormous amount of Zod schemas and unit tests around them. Yeah, I know someone will say that people don't read code anymore anyway. But I do. I still like code, and I still have doubts about the quality of coding agents, but that's another topic ;)

Long story short, I experimented with the TypeScript compiler and built a small playground showing how I imagine runtime types could work in TypeScript.

https://nola.sh/playground/?example=types

I know why Jev became popular: https://x.com/mykhailen/status/2102219600192565586?s=20

Hi all builders,

I've been building Nola for the last 3 months. Even slept a bit sometimes.

Finally released it a week ago and got 4 GitHub stars. Yooohooo

It was worth it. 4 f*king stars.

I'm living proof that sometimes we overcomplicate things. Start smaller, release sooner, and don't try to build everything at once.

But I keep going

This 4-star legend: https://github.com/nola-lang/nola

Oh yeah, that’s awesome! Thank you. You guys created a really great tool, it’s so motivating!

Great point! Actually, it's already part of the parser but not fully implemented. However, it's coming very soon!

Thank you so much :)

It was funny that when I was in the middle of the project, I discovered Hurl. It was cool, especially since it's written in Rust and uses libcurl under the hood. However, the lack of OpenAPI support and VS Code integration forced me to continue working on HTTL project.

Yeah, I agree. Bruno is a great tool, but it's missing one key component that I needed (maybe it's just me) – it can't run multiple requests in a chain. Also, constructions like: get { url: .... } feel too verbose to me, I wanted something clearer, like: get /users ;) But in general, thank you guys for your interest, my goal is to gain that 30k+ starts )))

Thank you all for showing interest in this project. You described exactly what motivated me to create this language – support for OpenAPI specs. I just wanted to have a language where I could import an OpenAPI spec and leverage the intelligence, because, like you, in all my projects the specs were autogenerated.

I'm so glad you liked it! Thank you for the feedback. Yes, I'm working on adding CLI support as well as support for other IDEs. Regarding the query string, you could just use a regular form: `get https://reqres.in/api/users?page=2` or (if you already specified a base url) `get /users?page=2`