How to make fragment refetchable by using client preset of codegen?

Agreed. Haven't tried it for a while but I remember that when generating react hooks to query your data (for example useQueryBooks to return the GQL query "Books"), the return type of the hooks function wasn't set in the .ts file, thus making the linter shouting when the option to force the return type of a function is set in the tssonfig file. Is it "fixed" ?

Aren’t they planing on deprecating the apollo cli tool?

@@laesseV Yes I think it doesn't even work with the latest Node versions

This makes me go nuts using Strapi.

Did I? Was this requested?

@@mattpocockuk yep, I asked you a couple of videos ago to tell about a code generation and you liked my comment 😉

@@artemstratienko4842 You planted the seed! Thanks!

Absolutely. It can be so annoying.

I feel your pain. Yes. When code gets checked into the server, git has no feedback mechanism to push it to local branches watching. git is not real-time. It could be. Then CI/CD & such could chain from shared source branch changes. When schema changes, we want it to break elsewhere.

commiting generated code to git is like commiting object files to git in a c project. generated code is an intermediary artifact that happens to be code

@@animanaut Not necessarily. There should be a two-way binding between generated code and the original document. Such that a change to the generated code can parse back into the document. With that in mind, there is nothing wrong with checking both in. And even if you change generated code and it diverges from the documentation it was generated from, that diff should be preserved.

@@jrgalyen i've been there, never doing this again. generated code is most of the time a one way street so you better treat it as intermediary by default. other languages like java put generated code into the target folder by default. modifying generated code will bite you in one way or the other in my experience. if the codegenerator cannot produce the code you need you might have to rethink its usage in the project.

@@animanaut Except for ORM's and Data Contracts like OpenAPI generating POCO objects. Stuff you shouldn't be writing tests for anyways. I wasn't saying code generation for anything outside boiler plate.

Is that project open source ? If the code is accessible-enough maybe you could get a hand ? (from me or others interested in this)

@@elfelipe1996 it is, but I want it to be in somewhat of a shape before I tell anyone where it is. I'll get back to you one of these days 😉

@@Stmated understandable. Good luck with it!

@Stmated A mammoth undertaking! Hope it works out. Used OpenAPI TS generator tools for years and the dev experience wasn’t great. Would be amazing if a high quality alternative would be available. Good luck!!

Which openapi generator? Give them a taste of deno to convince them of javascript on backend. Avoid node like the plague :) Deno was created by the author of node. one executable. Generates binaries.

Is the course in deno?

Sounds interesting, can you please share a link for that?

27 minutes was the maximum for autocomplete here. I really hope stc becomes useable soon. Been slamming "as any" all over the codebase to speed the typechecker up.

@@michaelbitzer7295 Damn, that sounds like a nightmare.. 27 minutes? might as well be turned off..

@@ColinRichardson It was a nightmare at times, but after a ton of manual typing it now sits at around a second, so it is somewhat bearable.

@@michaelbitzer7295 Ahhh.. Sadly, my slowdown is almost constant.. I type a few lines, says it doesn't know a Type, I tell it to import it, and I have to wait 30 seconds for the list of things... I have got to the point of having the "search as a panel" open all the time, so I can quickly search for somewhere it's been imported before and copy-paste... It's quicker than having the IDE do it for me.

tho not gonna lie, at least prisma is trying to be better

@@dylan_the_wizard amazing! Thank you very very much for you reply!

you want a single source of truth for data and data contracts. You want a single source of truth here. Right? right? *cwies*

Would you mind to elaborate?

Great question, worthy of a video itself

@@mattpocockuk I'd love to know your take on this. Especially on cases where it's not a javascript monorepo and the backend is also not typescript / javascript. Because all of the cool tools out there like tRPC are not really an option for me because the backend in my project is python mostly

+10000

​@@GerardoSabetta can't you use OpenAPI/Swagger with Python? Where I work, backend is done in .NET Core and backend developers add annotations to endpoints and we get a full OpenAPI spec generated from that. Then on frontend we just use a tool like "swagger-typescript-api" to generate a full API client using fetch or axios and we just update it periodically when backend changes. Yeah it's a minor inconvenience to re-generate that API client, but it's way better than just copying types from backend code or trying to type them using responses that we would get calling that API. We wouldn't be able to even cover all types easily like that. In your case, I would personally go for documenting the backend using OpenAPI because that can also generate simple documentation page that can be used for testing various endpoints without having to set up the project at all. Then use a codegen step whenever needed on frontend and that's it.

@@rand0mtv660 That's great advice, yes, we can use swagger with python, but since it's not a monorepo, running the codegen is not as easy as being in the same branch as your backend dev. We would need to publish a package with the yml for the open API and consume it on the frontend repo. It's definitely doable

Yep, this works well - but is more annoying when you have objects more than one level deep.

@@mattpocockuk Yes, sometimes you have to just declare it a type like `type BookCollectionForLandingPageToy` and pass that around locally. Still imo much preferred to being stuck unable to remove an expensive field that's only used in a handful of places from a query because you've used that query everywhere and this one part of the app would just go entirely red if you dared pare down how much data you're asking for unnecessarily

Sounds like you're describing Prisma, not tRPC?

​@@mattpocockukOh, yeah. It's Prisma. My bad. I've mistaken bare tRPC for create-t3-app.

yes that's what the --watch flag does. As pointed out in the video, in very large projects, this starts to really slow down

BE can generate the schema.ts then release a new package version for FE

mattpocock.com/faqs

Yes - but other codegen tools suffer the same problem and don't have a built-in abstraction like fragments to solve it.

That is exactly what I am working on as a side-project. The steps it takes for each generation is: 1. Read input schema 2. Convert into common model 3. Convert common model into an Abstract Syntax Tree (like "class/type" with "properties/accessors", not bound to output language specifics) 4. Convert Abstract Syntax Tree into a Concrete Syntax Tree (now locking it into the form of the output language) 5. Convert CST into output strings by running a chosen renderer over it Each conversion between the different steps is done with appendable transformers that can be added/removed depending on your need. This way I can easily build a "convert fields into getters and setters" for multiple languages on the AST level, et cetera. Reuse as much functionality for as many different languages as possible. It works surprisingly well so far. I just need to find more time to actually make it usable and not just a Proof of Concept running test cases.

> dozen of programming languages and frameworks What the hell