We want to maintain thousands of React examples, but the starting point is that we've got all of these as Vanilla TypeScript examples. ![]() And so ASTs, that's going to be our axe and that's how we're going to complete these tasks. And if we have got an axe to hand, we're going to make sure we know how to use it and that it's sharp and ready to go. So the idea here is, instead of just jumping straight into a task, we're going to make sure we're using the right tool. So give me six hours to chop down a tree and I'll spend the first four hours sharpening the axe. So this is where we get to this quote, which is or maybe not from Abraham Lincoln. You could, but probably don't want to do it. You know, that type is then, you need to move down the hierarchy a bit more, so you find those interfaces, add it in, and you see it's just this kind of cycle which is a bit slow and tedious and a bit error-prone as well. You could find where you use row data, go in there, change the type, rebuild. So for this one, you could do the brute force approach. So you can pass this interface to our AgGrid React component, and then we need it to flow through everywhere else where you might have a callback or handlers. So there's no real brute force approach for that.Īnd then if we look at the second task, which we'll try and solve, is we're adding this generic typing across hundreds of interfaces. Because if you're going to do it manually, you're going to have to employ lots of people, you're going to make mistakes, your documentation is going to be buggy and no one is going to win. So hopefully you'll be like, I'm not going to do that manually. And then there's two different ways you can import AgGrid across 500 different feature examples. As I said, we've got three versions for classes, hooks, hooks with TypeScript. ![]() So in our docs, you'll see a lot of these examples.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |