"Value is not accepted" / Code analyzer rules not recognized in ruleset file.
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 881
- Forks
- 285
- Avg merge
- 3d 36m
- Merged PRs (30d)
- 1
Description
1. Describe the bug
I have a ruleset.json in my project. Since the update to AL language v18.0.2732683, all code analyzer rules (including custom ones like ALCops) listed here are marked as unknown. "Value is not accepted. Valid values:"
Known are only compiler warnings (AL*):
Could it be related to this change?
2. To Reproduce
Create a ruleset.json file and add the following rule to it:
"rules": [
{
"id": "AA0005",
"action": "Warning",
"justification": "Whatever"
}
3. Expected behavior
The AL language should recognize all code analyzer rules.
4. Actual behavior
See above.
5. Versions:
- AL Language: v18.0.2732683
- Visual Studio Code: 1.137.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ruleset.json reproduction and the AL Language v18.0.2732683 extension behavior in Visual Studio Code, using rule AA0005 and a custom ALCops rule as examples. Verify which rule IDs the editor accepts and compare that with the expected recognition of all code analyzer rules; done means those entries are no longer marked as unknown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100