microsoft / microsoft/AL

aa0021 not recognizing fieldref and recordref out of order

Open
#8,155 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted documentation
Dominant language
PowerShell
Stars
881
Forks
285
Avg merge
3d 36m
Merged PRs (30d)
1

Description

Please include the following with each issue:

1. Describe the bug
FieldRef ordered above RecordRef not producing warning.

2. To Reproduce
declare these vars:

        salesHeader: Record "Sales Header";
        fldRef: FieldRef;
        recRef: RecordRef;

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.

3. Expected behavior
trigger rule aa0021

4. Actual behavior
fieldref not underlined for incorrect sort

Image

5. Versions:

  • AL Language:16.2.1869542
  • Visual Studio Code:1.1.05.1
  • Business Central:any
  • List of Visual Studio Code extensions that you have installed:al language
  • Operating System:
    • Windows
    • Linux
    • MacOS
Final Checklist

Please remember to do the following:

  • Search the issue repository to ensure you are reporting a new issue

  • Reproduce the issue after disabling all extensions except the AL Language extension

  • Simplify your code around the issue to better isolate the problem

Internal work item: AB#613207

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the AL Language extension using the provided salesHeader, fldRef, and recRef declarations, with rule aa0021 and the listed extension version. Compare the expected warning with the current behavior; done means the incorrectly ordered FieldRef and RecordRef are identified as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
compilers, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.