Posts

Showing posts from November, 2022

Making all service APi's generic

 So, I was looking into an issue in which one our customer complaint about inconsistency of some of our interfaces. He specifically talked about status code of some of our API's and mentioned that some status codes are supported by some API's and not by others. What can I do to mitigate it? Improve up the documentation with details [asked by customer]. Look into the code: Code says that we are specifically handling this error (not found) and adding it inside the response. There might be some reason associated with it. How can I figure out the reasons? Check code commits Ask Product manager Some comments around that code Documentation of this feature or maybe issue fix for this bug  Asked for clarification from Product Manager let's see what happens.

Demystifying Error response

 So, I was looking into a bug in which my client was complaining that they are getting a generalized error message and specific message relating to that error was absent. So, I did an initial code analysis and found that the log was returned by us, but we are also sending using up an err message from backend and seems like that was coming to be as empty.  So, what can I do to mitigate it? I can raise it to my backend team. Check backends team code and figure out if something is going wrong during the parsing or mapping the response. Can something specific be added inside my code?? Things are breaking from backends' side so probably I might not be knowing the reason behind it. Unless I get it from backend. So, after going through the code investigating more, I found that point 2 was valid the issue was with parsing/mapping of response. So, I fixed it up and wrote verification test and raise a pull request.

Understanding VS code launch.json file

Image
 I have recently moved to other organization and here my team is extensively using VS code. So, I was assigned a task and after coding it up I was planning to test it. This is the button on which I clicked. Immediately after that, I start seeing a pop in which VS code asked me setup up a launch.json file in order run my tests. I was little bit confused about what exactly is this launch.json is and why it's needed? I did search for this, and this was the first article to which I found link:  Debugging in Visual Studio Code After reading it up a bit, I found that this is a configuration file needed for running up the tests and currently in my code I haven't configured it. Upon reading more I found that vs code does provide options to run current file but it's better to create a launch.json file to save and configure testing details . Info: This launch.json file would be created under .vscode folder. There are quite a lot of launch.json attributes which can be used based upon...