5
mrstebo
7y

Adding a new feature to a mobile app that has a bunch of classes for getting URLs! Want some examples?

FallbackUrlProvider
CompositeUrlProvider
CompositeRouteUrlProvider
CompositeBaseUrlProvider
RootUrlProvider

I was half expecting to find FallbackRootBaseCompositeUrlProvider!

Not only that, but there were a load of interfaces that sometimes didn't match the name of the class!!!

For example,

class RootUrlProvider : ICompositeUrlProvider

Ugh! But I managed to get the new feature in... Somehow... After trying something... Throwing it away... Trying something else... Throwing it away...

😭😭😭

Comments
  • 0
    What... Why? What were they doing?

    I swear if they're all dummy string concats I'll be not happy.
  • 0
    They were providing URLs apparently... 👀

    Some even had an extra provider to include the paths... That also had a method for getting a path using an enum (should have a factory instead for stuff like that).

    And then yeah... Most were just concatenating from a base URL brought in from somewhere else...

    It's been a long day 😒
  • 0
    Ow shet 🤔
Add Comment