microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
719 stars 242 forks source link

AA0218 should no longer trigger on pages if ToolTip is defined on a table field #7696

Closed tinestaric closed 3 months ago

tinestaric commented 3 months ago

1. Describe the bug

When moving the ToolTip from the PageField to the TableField, AA0218 is still triggered on PageField.

2. To Reproduce

image

image

Page:

page 30163 "Shpfy Metafields"
{
    Caption = 'Shopify Metafields';
    PageType = List;
    SourceTable = "Shpfy Metafield";
    UsageCategory = None;
    ApplicationArea = All;

    layout
    {
        area(Content)
        {
            repeater(Metafields)
            {
                field(Namespace; Rec.Namespace)
                {
                }
            }
        }
    }
}

Table:

table 30101 "Shpfy Metafield"
{
    Access = Internal;
    Caption = 'Shopify Metafield';
    DataClassification = CustomerContent;
    DrillDownPageId = "Shpfy Metafields";
    LookupPageId = "Shpfy Metafields";

    fields
    {
        field(1; Id; BigInteger)
        {
            Caption = 'Id';
            DataClassification = SystemMetadata;
            Editable = false;
        }

        field(2; Namespace; Text[255])
        {
            Caption = 'Namespace';
            DataClassification = SystemMetadata;
            ToolTip = 'Specifies the namespace of the metafield.';
        }
    }
}

3. Expected behavior

No warning, if ToolTip is defined on Table Field

4. Actual behavior

Warning on Page Field, even though ToolTip is defined on the Table Field

5. Versions:

BazookaMusic commented 3 months ago

Thank you for reporting this. We know about this bug already and it will be fixed soon with the next release of the extension.

BazookaMusic commented 3 months ago

This should be fixed in the latest release.