Capaj
Joined 14 years ago
Karma
-3
Submissions
9
Member since
Jun 14
Recent submissions
Comment · 3 months ago
yes that is exactly the main usecase for this
Comment · 3 months ago
I use it as my daily driver for any git operations, but most people prefer command line.
So for a typical person it is useful early in their developer career as a helper when learning git.
Comment · 3 months ago
I was a disgruntled user of ungit for the past 10 years. Even considered rewriting it myself manually like 5 years ago. Well not anymore.
In the past few weeks I built a fast, animated git GUI from scratch
ingit makes branch switching, merge previews, rebases, cherry-picks, and reflog recovery feel instant. I would highly recommend especially if you're new to git.
Try with npm i @ingit/cli
Comment · 5 years ago
No it's not. Even if they fixed all the bugs which I doubt the API design is bad.
Comment · 6 years ago
> It's great for the frontend, but in this case it's awful for the backend.
So what you are saying is it's better to leave this complexity for the frontend developer to handle on the client side? Very wise!
Comment · 7 years ago
> If an ID is required for all queries the docs should say so.
they absolutely should. It's not really needed every time, but when you have a queries with IDs and without-that's when the cache blows up. They even a have a snapshot test for this unfortunate behavior: https://github.com/apollographql/apollo-client/blob/master/p...
Comment · 7 years ago
> Also IDs aren’t required for cache updates, only the typename.
this is very inacurate. The problem happens when an items is cached with an ID and then another GraphQL request tries to cache it without and ID or vice versa. This is where the apollo-cache-inmemory blows up with an error like this: https://api.media.atlassian.com/file/f82c0ee8-2412-4f1b-8027...
There's even a test for this unfortunate behavior: https://github.com/apollographql/apollo-client/blob/master/p...