Managed assertions in an integrated development environment
The present disclosure relates to maintaining assertions in an integrated development environment (IDE) tool. According to one embodiment, the IDE receives a request to add an assertion at a specified location within source code of an application from a user interacting with an integrated development environment (IDE) tool. The source code is stored in a first file associated with a development project. The IDE tool receives a definition for the assertion and stores the definition for the assertion in a second file associated with the development project. The IDE tool creates an association in the development project between the source code of the application and the assertion.
1. A method for managing assertions, comprising:
receiving, from a user interacting with an integrated development environment (IDE) tool, a request to add an assertion at a specified location within source code of an application, wherein the source code is stored in a first file associated with a development project and wherein the first file does not include information about the assertion;
receiving a definition for the assertion, wherein the definition includes one or more lines of source code, an expiration time, and a number of times to insert the assertion into the source code, when compiling the application from the source code;
storing the definition for the assertion in a second file associated with the development project;
creating an association in the development project between the source code of the application and the assertion, wherein the association is not stored in the first file and indicates at least a line in the first file at which to insert the assertion prior to compiling the source code;
receiving a request to compile the source code of the application;
modifying the source code stored in the first file by inserting the one or more lines of source code included in the assertion definition at the specified location in the source code; and
compiling the application from the source code in the modified first file.
2. The method of claim 1 , wherein the definition includes one or more of:
a scope defining one or more users with access to the assertion; and
an indication whether the assertion is static or dynamic, wherein a static assertion is inserted into the source code before the application is compiled from the source code and wherein a dynamic assertion is inserted at into the source code dynamically when executing the application.
3. The method of claim 1 , wherein the one or more lines of source code include a condition assumed to be true at the specified location.
4. The method of claim 1 , further comprising:
receiving a request to edit the source code stored in the first file;
identifying the specified location in the source code of the assertion based on the association between the source code of the application and the assertion; and
presenting an indication of the assertion in an editing pane of the IDE tool at the specified location.
5. The method of claim 4 , wherein the indication identifies a scope of the assertion.
6. The method of claim 4 , wherein the indication identifies whether the assertion is active or inactive.