6.8.1.2810

Major release with support for the new SharePoint Framework (SPFx), SonarQube and Gulp, including some fixes.

Features

• Support for SharePoint Framework (SPFx): Analysis of SPFx projects with over 50 rules, metrics, and inventories.
• Support for Analysis via Gulp: Ability to run analysis in Visual Studio Code via Gulp.
• Support for SonarQube: Ability to run SPCAF analysis in SonarQube.

Bug Fixes

• Fixed issue in Visual Studio: build with SPCAF analysis failed if C# 6.0 language features are used.

New Rules for SharePoint Framework (SPFx)

Correctness

• SPF019801 : Define the solution name property
• SPF019802 : Define a version number for your solution
• SPF019803 : Ensure that the solution version number is valid
• SPF019804 : Define a valid id for your solution
• SPF019805 : Ensure that the solution id is valid
• SPF019806 : Specify a bundle entry point
• SPF019807 : Bundle entry point must point to a valid project file
• SPF019808 : Specify a valid bundle entry output path
• SPF019809 : Specify solution configuration in the package-solution.json file
• SPF019810 : Specify solution paths configuration in the package-solution.json file
• SPF019811 : Bundle entry output path must be located under the dist folder
• SPF019812 : Specify the path of the zipped package in the package-solution.json file
• SPF019813 : Specify component type in the manifest
• SPF019814 : Specify valid component type in the manifest
• SPF019815 : React event handlers are defined using camelCased properties
• SPF019816 : Define CDN base path
• SPF019817 : Specify valid CDN base path
• SPF019901 : Specify the Web Part Id
• SPF019902 : Don’t use the same id for multiple web parts
• SPF019903 : Specify the Web Part Title
• SPF019904 : Web Part Title must not be longer than 100 characters
• SPF019905 : Specify Web Part version
• SPF019906 : Specify valid Web Part version
• SPF019907 : Specify the Web Part manifest version
• SPF019908 : Specify valid Web Part manifest version
• SPF019909 : Web Part Description must not be longer than 255 characters
• SPF019910: Specify Web Part Properties
• SPF019911 : Specify valid Web Part Id
• SPF019912 : Use a valid font icon as Web Part icon
• SPF019913 : Ensure that Web Part properties used in code are defined in the Web Part manifest
• SPF019914 : Ensure that Web Part properties specified in the manifest are used in code
• SPF019915 : Specify the Web Part Description
• SPF019916 : Specify Web Part image
• SPF019917 : Don’t specify both Web Part icon and Web Part image
• SPF019918 : Specify valid Web Part image URL
• SPF229901 : Client Side Web Part doesn’t use optimized scripts

Security

• SPF029901 : Don’t reference scripts from unapproved locations
• SPF029902 : Don’t load Web Parts from unapproved locations

Best Practice

• SPF059801 : React component files should have correct extension
• SPF059802 : Specify TypeScript linting rules
• SPF059803 : File that doesn’t define React component shouldn’t use the .jsx/.tsx extension
• SPF059804 : Project should list its dependencies in package.json or as external resources

Performance

• SPF229801 : Project doesn’t exclude standard dependencies
• SPF229802 : Don’t include the same modules in multiple bundles

Tags

SPCAF | Release Notes | 6.8.1.2810