Release Notes - 2.10
2.10.3-funcrel
Other Updates
| Details |
|---|
| Fixes the missing URI property in HTTP request objects from the ‘request’ library, allowing them to be correctly linked by wbslinker. |
| Fixes the GUIDs of some objects. |
| Fixes the incorrect MongoDB collection object name. |
| Removed the unnecessary logging. |
2.10.2-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 44497 | Improve support of Knex.js to prevent erroneous "Unknown database" type objects from being created. |
Other Updates
| Details |
|---|
| Sensitive Data Tagging for NoSQL Collections has been added. See https://doc.castsoftware.com/technologies/multi/data-sensitivity/. |
| Sensitive Data Tagging for Cloud File Storage. See https://doc.castsoftware.com/technologies/multi/data-sensitivity/. |
2.10.1-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 42184 | Remove a false positive violation of the rule 1020748 "Avoid using the call of data service with Node.js inside a loop". |
Other Updates
| Details |
|---|
| The behaviour of the extension has been updated to ensure that when an SQL query is found, the corresponding NodeJS Unknown Database Table objects are now handled by the com.castsoftware.nodejs.missingtable extension (previously com.castsoftware.nodejs handled these object types). |
| The parsing of gRPC .proto files has been improved. |
| Updates have been implemented to remove unnecessary com.castsoftware.nodejs related log messages. |
| Updates have been implemented to ensure that the correct caller of a REST reception operation (when using Sails.js) is resolved (the caller was previously incorrectly set to the parent file rather than the method). |
2.10.0-funcrel
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 41052 | Fixes an issue causing missing "Node JS Post Operation" objects and therefore missing links. |
Other Updates
| Details |
|---|
| A change in behaviour has been implemented: "Azure Functions" are now set by default as entry points when they are not called by any other object. |
| A change in behaviour has been implemented: gRPC objects are now defined as entry/exit points. |
2.10.0-beta1
New Support
| Summary | Details |
|---|---|
| Support gRPC | gRPC (https://grpc.io/) is now supported. See https://doc.castsoftware.com/display/TECHNOS/Node.js+-+2.10+-+Analysis+Results+-+gRPC. |