Using Repository Service Patterns in GitX

GitX hides a lot of what makes flutter flutter, something like that. So you would be screwed if there was a big change that GitX no longer worked and you'd be relying on somebody to fix it for you. But in terms of architecture and code, I've noticed that having two classes where you make the request and handle one part when you make a request, one class that calls that class and handles all of the exceptions,. And then returns a functional programming style of handling errors to the UI or to the class calling that service. Kind of reduces a lot of unnecessary boilerplate in the codethat you don't usually want to have a lot of boilerplate.