Release notes
7.15.0.0
In this maintenance release, we have some issues with analysis execution and reports.
New Features
- Improved operation on Linux machines.
- Added O365 compatability rules.
- Added React rules.
- Added site definition inventory.
- Added webpart class inventory.
Bug Fixes
- Fixed issues in SPFx rules with approved locations for external scripts
- Fixed issue with extraction and deletion of the temp folder.
- Fixed an issue that could cause an exception in the Code Metrics Report under certain circumstances.
- Fixed an issue where SPC019105 was not picked Up Correctly In PowerShell.
- Fixed an issue where Javascript rules could misidentify line details reported in reports.
- Fixed an issue where a subscription license always warns it is due to expire.
- Fixed an issue where Angular analyzers slow down SPFx analysis.
- Fixed an issue with SPF050602 which could return false positive.
- Fixed an issue with SPF020802 under certain circumstances could throw exceptions.
- Fixed an issue with SPF010716 under certain circumstances could throw exceptions.
- Fixed an issue with SPC058701 under certain circumstances could throw exceptions.
- Fixed an issue with FileNotFoundException Rencore.Analyzers.JavaScript.VulnerabilitiesDb.Model when running analysis using the CodeAnalyzer.
New React Rules
-
Correctness
- RCT010101: Don’t use “return false” in the React event handler.
- RCT010102: Style property of a React DOM element should be an object.
- RCT010103: Don’t specify children when using dangerouslySetinnerHTML.
- RCT010104: Don’t pass HTML as a string to the “dangerouslySetinnerHTML” property.
- RCT010105: Don’t use Generator as a child of a React element.
- RCT010106: Don’t check the “array.length” property when conditionally rendering elements.
- RCT010107: React lifecycle method does’nt return a valid value.
- RCT010108: Don’t override React component methods suppported only in createReactClass() in ES6 class component.
- RCT010109: Don’t specify React event handlers as a string.
- RCT010110: Don’t use invalid CSS style names and values.
- RCT010111: Don’t use the return value of the “ReactDom.remder ()” method.
- RCT010112: Don’t use incorrectly spelled React API’s.
- RCT010113: Don’t use incorrect casing for DOM attributes and properties in React.
- RCT010114: Don’t access special React properties.
- RCT010115: The initial state in ES6 class component is not an object.
- RCT010116: Don’t call “setState” in specific lifecycle methods.
New Office 365 Rules
-
Compatibility
- SPC170727: SiteDefinition references VisibilityFeatureDependency which is not transformable.
- SPC170728: SiteDefinition references ProvisioningAssembly which is not transformable.
- SPC172132: Feature contains FeatureReceiver.
- SPC172134: Feature has scope ‘WebApplication’ or ‘Farm’ Warning.
- SPC175122: Field contains resource keys.
- SPC175123: Field based upon custom field type.
- SPC175124: Field has no ID value set.
- SPC175125: Calculated field outputs HTML encoded string.
- SPC175222: ContentType contains complex to transform event receiver code.
- SPC175223: ContentType inherits unknown parent ContentType.
- SPC175224: ContentType inherits custom parent ContentType which needs to be provisioned before.
- SPC175225: ContentType references a custom Field which needs to be provisioned before.
- SPC175226: ContentType references an unknown Field.
- SPC175230: ContentType uses DocumentTemplate.
- SPC175230: ContentType references DocumentTemplate in Layouts folder.
- SPC175233: ContentType contains resource keys.
- SPC175422: List instance contains resource keys.
- SPC175423: Field Reference has no ID value set.
- SPC175722: Custom Action contains a reference to the layouts system folder.
- SPC175723: Custom action contains resource keys.
- SPC175724: Custom Action contains a reference to the admin system folder.