Sometimes ThingsDB will generate a change while you know it is not required.
A common example is the following:
response = {};
response.test = "message"; // this will create a change as ThingsDB doesn't know that response is not stored
response;
We know that ThingsDB does not require a change, however one will be created.
With the new function nse() we could promise ThingsDB that no change is required.
The function nse() will only work for chained function calls and assignments. Therefore calling wse() will create a change and will make a call to nse() obsolete. The nse() function should raise an error in the latter case as the usage is not legit.
Type of change
Please delete options that are not relevant.
[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update
How Has This Been Tested?
[x] Test Collection functions
Checklist:
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes
Description
Sometimes ThingsDB will generate a change while you know it is not required. A common example is the following:
We know that ThingsDB does not require a change, however one will be created. With the new function nse() we could promise ThingsDB that no change is required. The function nse() will only work for chained function calls and assignments. Therefore calling wse() will create a change and will make a call to nse() obsolete. The nse() function should raise an error in the latter case as the usage is not legit.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist: