Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rule AS0098 is not forced for report labels. #7141

Closed
3 tasks done
pri-kise opened this issue Aug 23, 2022 · 2 comments
Closed
3 tasks done

Rule AS0098 is not forced for report labels. #7141

pri-kise opened this issue Aug 23, 2022 · 2 comments
Labels
accepted AppSourceCop This is a specific static-code-analysis group (AS) ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release static-code-analysis

Comments

@pri-kise
Copy link

pri-kise commented Aug 23, 2022

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/analyzers/appsourcecop-as0098

Please include the following with each issue:

1. Describe the bug
The rule AS0098 should be applied on new defined labels of report extensions, too.

2. To Reproduce
Steps to reproduce the behavior:

  1. Create a new Report Extension without Affix on the label name.
reportextension 50000 "XXX Put-away List" extends "Put-away List"
{
    labels
    {
        WhseActLineSourceCaptionTest = 'Src.';
    }
}

3. Expected behavior
Rule AS0098 should apply for labels of report extensions, too.

4. Actual behavior
There is no warning.

5. Versions:

  • AL Language: v9.4.663067
  • Visual Studio Code:
    Version: 1.70.2

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

@pri-kise pri-kise changed the title Rule AS0098 is not force for report labels. Rule AS0098 is not forced for report labels. Aug 23, 2022
@thloke thloke added static-code-analysis AppSourceCop This is a specific static-code-analysis group (AS) accepted labels Aug 25, 2022
@JesperSchulz JesperSchulz added the ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release label Sep 22, 2022
@JesperSchulz
Copy link

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 22.0.46748.0 and VS Code Extension Version 11.0.683324.

If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo

For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/

@JesperSchulz
Copy link

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 22.0.46748.0 and VS Code Extension Version 11.0.683324.

If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo

For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted AppSourceCop This is a specific static-code-analysis group (AS) ships-in-future-update The issue is fixed in our 'master' branch and will ship in the next PREVIEW release static-code-analysis
Projects
None yet
Development

No branches or pull requests

3 participants