Understanding VS code launch.json file

 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 the requirements:
Debugging in Visual Studio Code also intellisense can also be used to find out the desired supported attributes for the platform.

There is also a subsection related to variable substitution: Debugging in Visual Studio Code
which talk about vs code assigning names to commonly used up paths. I found it quite useful in understanding some of the variables like ${workspacefolder} --> root path of current project, or ${file} --> current open file.

There is also one more subsection for defining up operating system specific properties. 
There was also an example mentioned in this document see screen shot above. It shows that stopOnEntry variable would be true for all platforms except macos.

Further this talks also talks about a lot of advanced vs code topics but let's leave it for another time for now.



Comments

Post a Comment

Popular posts from this blog

Kustov query language

Image
 In this post I would be talking about my experiences of learning KQL (Kustov query language). I started with this document  Kusto Query Language (KQL) overview | Kusto . From the documentation I get to know that it's a query language used for analytics purposes and uses up schema entities quite similar to SQL i.e., having database, tables, column. Then, document further talks about Kusto query which is basically a read only query for processing data. Types of querying: KQL supports 3 types of query statements. These are basically Let, Set, Tabular. Tabular: This is the most common way of querying. In this format a table is provided as an input and table is also taken up as output. Query consists of lot of operands which are connected by pipe (|). I know it's too much but let's take a look at a query and this would be crystal clear.  In this query we can see StormEvents is provided as input and then there are lot of operands which are connected using pipe (|). These pip...
Read more

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.
Read more

How I learned LINQ query Fundamentals

Image
Some days back, I joined my new organization, and I came to know that my team extensively uses c# for their development purposes and I came from java background. By surfing through internet and watching some videos I was able to grasp basics of c# then started exploring code base my team. I saw that there are quite a lot of code pieces like: I found it bit difficult to understand as these are not part of c# syntax so after doing some google searches, I found that this is part of something called LINQ(Language-Integrated) queries which provides solution for object-relational mapping and simplifies operation between objects and data sources. Obviously, I had to learn more about it and become an advanced user, as my team is using it extensively.  Random thought: Yeah, it's okay I have to learn LINQ queries since my team is using it but why exactly they are using it?? Let's analyze advantages of LINQ: Familiar language: Developers don't have to learn a new query language for ...
Read more