Release Notes - 2.0

  • 2.0.0-funcrel
    Fixes missing links between some SAP Views and SAP Tables, or from foreign keys
    Fixes false positives with rule: 💎 8578 - Avoid using MODIFY without Authorization Check 📝 56694
    Fixes missing violations with rule: 💎 8120 - CALL FUNCTION without error handling
    Updates documentation of rule: 💎 7518 - Avoid missing WHEN OTHERS in CASE statements 📝 57505
    Improves accuracy of rule: 💎 8106 - Avoid empty IF-ENDIF blocks 📝 58034
    Fixes violations positions of rule: 💎 7512 - Avoid empty Functions, Forms and Modules
    Fixes analysis of some classes having declaration and implementation in different files, and not inside classpools
    Fixes missing violations of rule: 💎 1104018 - Avoid empty catch blocks (ABAP)
    📝 55834 Adds new rules: 💎 1104010 - Avoid Classes with a very low comment/code ratio (ABAP), 💎 1104012 - Avoid Interfaces with a low comment/code ratio (ABAP), 💎 1104014 - Avoid undocumented Classes (ABAP), 💎 1104016 - Avoid undocumented Interfaces (ABAP)
    Updates paths of ABAP files used for bookmark when they contain double path separators (\\)
    Updates documentation of rules about classes/interfaces: 💎 1104010 - Avoid Classes with a very low comment/code ratio (ABAP), 💎 1104012 - Avoid Interfaces with a low comment/code ratio (ABAP), 💎 1104014 - Avoid undocumented Classes (ABAP), 💎 1104016 - Avoid undocumented Interfaces (ABAP)
  • 2.0.0-beta1

    Initial release of the extension compatible with CAST Imaging V3. Requires CAST Imaging 3.5.5-funcrel or later and com.castsoftware.imaging.core 8.4.8 or later. Functionally equivalent (i.e. includes all fixes and changes) to com.castsoftware.sap 1.0.19. Please take note of the section Extension equivalence which explains some of the result changes in comparison to previous releases.

    Note that in this beta release, the rule: 💎 8120: “Avoid using CALL FUNCTION without error handling” is missing and will therefore not be calculated during an analysis. This known issue (SAP-436) will be fixed in a future release.

    ABAP Processing Screen objects have been categorised as Entry Point objects. This improves the accuracy of the transaction information provided in the analysis results. This change means that results may differ when comparing the analysis of the same application actioned using the 1.0.19 or earlier releases of the com.castsoftware.sap extension.