The add() function (that is available in the source code) basically uses some built in debugging tools to find out where in the code the function is called, and then parses the comment from the file and uses it for adding stuff.
I’ve never tried (becuse why would you…) but something similar can probably be built in any interpreted language
It’s not something Python does by design
Nah thanks, up arrow hasnt failed me yet
I know you wrote /s, but this has basically nothing to do with the tech of microservices, and more to do with internal politics.
Switch the ”user microservice” to ”birth date is not indexed in the database and i have to reach out to the database handling team” and you are in the same situation
Tbh mostly microservices solves two issues for me:
You could do #2 in a ”monolithic” setup as well (by doing modules or libraries or something), it just never works out that way in practice
Imo they do not add problems, but they do exchange some problems for other problems.
Fix tpyo
Trust me, you do not want enthusiastic double gonorrhea.
I appreciate the text file in the image
Well, I mean, there are no ghosts there now!
Ah, the God Force 1
With a honey in the middle there’s some leeway
Missing neighbour drilling on saturday morning
I work with programming, and I used to think this was the case. The reality is that I just do it even more as a hobby as well.
This specific use case? To make a meme, mainly ¯\(ツ)/¯
As for the components: Parsing comments have been used for stuff like type hints / formatting / linting, tho generally not at run time (afaik).
The tooling for finding out where something is called from can be used to give a better understanding of where things go wrong when an exception happens or similar, to add to logs.
I would say that in general you don’t need either functionality except for certain edge-usecases