Follow
Seeing a typo in an open-source project, going to submit a patch, being unable to find where the typo actually lives in the codebase because contemporary frontend code makes me feel like I’m looking at Solaris from Stanisław Lem’s book “Solaris” (1961).
@vruba if it helps at all: it’s very likely not the right choice
in fact,
@vruba This drives me nuts. Sometimes the text I'm searching for ends up being in one of the many dependencies, which is not part of the source code I'm searching. And all the layers of indirection really seem like overkill for the relatively simple functionality of the project.
It’s like 23 layers of indirection before you find an actual string that will actually appear on the actual user’s actual screen, and I’m sure this is the right choice, and is based on a lot of hard-won lessons about internationalization and ease of contribution and stuff, but … the string I’m looking for doesn’t even show up when I search?