-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #10 from Acumatica/feature/AC-333341-rework-groupi…
…ng-by-source-file Feature/ac 333341 rework grouping by source file
- Loading branch information
Showing
25 changed files
with
1,036 additions
and
586 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# CoreCompatibilyzer Release Notes | ||
This document provides information about fixes, enhancements, and key features that are available in CoreCompatibilyzer. | ||
|
||
## CoreComparibilyzer 1.1.0 (Current): January 23, 2025 | ||
CoreCompatibilyzer 1.1.0 provides new features and bugfixes described in this section as well as the features described below for previous versions of CoreCompatibilyzer. | ||
|
||
### New Features | ||
CoreComparibilyzer 1.1.0 introduces the following new features: | ||
- A way of grouping reported APIs by source files that contain the reported calls to incorrect APIs. | ||
- Support of ARM64 architecture in a Visual Studio extension. | ||
|
||
### Code Fixes | ||
CoreComparibilyzer 1.1.0 contains the following code fixes: | ||
- Incorectly banned APIs have been removed from the list of banned APIs incompatible with .Net Core 2.2. | ||
- Analysis of extension methods that were not recognized as banned APIs has been fixed. | ||
- Support for analysis of conditional access expressions (like `obj?.Member`) has been added. | ||
- Analysis of member access expression has been fixed by analyzing the type of the accessed expression. | ||
- Analysis of array type symbols has been fixed. | ||
- The `.editorconfig` file has been added to the CoreCompatibilyzer project to enforce consistent code style. | ||
- CoreCompatibilyzer code has been refactored to improve performance and readability. | ||
|
||
|
||
## CoreComparibilyzer 1.0.0: September 1, 2023 | ||
CoreComparibilyzer 1.0.0 is the initial release that introduces the following features. | ||
|
||
### Diagnostics | ||
CoreComparibilyzer finds usages of .Net Framework APIs incompatible with .Net Core 2.2 and reports them with one of the two diagnostics: | ||
|
||
| Code | Short Description | Type | Code Fix | | ||
| ------ | ------------------------------------------------------- | ----- | --------- | | ||
| [CoreCompat1001](diagnostics/CoreCompat1001.md) | The reported API is missing in the .Net Core 2.2 runtime. | Error | Unavailable | | ||
| [CoreCompat1002](diagnostics/CoreCompat1002.md) | The underlined API is not portable to .Net Core 2.2 runtime because the API is obsolete. | Error | Unavailable | | ||
|
||
### Visual Studio Extension | ||
CoreComparibilyzer provides an extension for Visual Studio to see analyzer alerts directly in the code editor. | ||
|
||
### Console Runner | ||
CoreComparibilyzer provides console runner to run the analysis from the command line for the entire solution or project manually or in CI scripts. The console runner also provides advanced options for report formatting style and output format. | ||
There are several available command line arguments that configure them. You can run `--help` to see the available options and their descriptions in the console window. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.