microsoft / microsoft/AL

AL Language extension enters a perpetual loading/spinning state when opening a multi-root

Open
#8,289 5 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

1. Describe the bug
The AL Language extension enters a perpetual loading/spinning state when opening a multi-root .code-workspace that spans two repositories: a documentation-only repository (opened as ".") and an AL source repository (opened as a sibling path). The extension never completes initialization ΓÇö IntelliSense, diagnostics, and CodeLens are unavailable.

Image

2. To Reproduce

Steps to reproduce the behavior:

  1. Check out both repositories side-by-side:

    <customer>-docs/          ← documentation repo (MkDocs, no app.json)
    <customer>/               ← AL source repo
    
  2. Open the workspace file located in the documentation repo:

    {
      "folders": [
        { "path": "." },
        { "path": "../<customer>" }
      ],
      "settings": {
        "al.enableCodeAnalysis": true,
        "al.codeAnalyzers": ["${CodeCop}", "${UICop}", "${PerTenantExtensionCop}"],
        "al.ruleSetPath": "ruleset.json"
      }
    }
    
    • "." ΓåÆ Documentation repository ΓÇö no app.json at root (MkDocs site, markdown only)
    • "../<customer>" ΓåÆ AL source repository ΓÇö contains 3 AL projects nested under subfolders:
    Subfolder App ID platform / application AL files
    W1/<customer>.w1 2bb1a09a-… 26.0.0.0 / 26.0.0.0 ~31
    BE/<customer>.be 3fe87366-… 26.0.0.0 / 26.0.0.0 ~5
    W1/<customer>.w1.Test 8b7b806d-… depends on W1 + MS test libs ~1
  3. Observe the AL Language extension status bar item.

  4. Wait ΓÇö the spinner never stops and the extension never becomes ready.

3. Expected behavior
The AL Language extension completes loading for all 3 AL projects found in the "../<customer>" folder and provides IntelliSense, diagnostics, and CodeLens normally.

4. Actual behavior
The AL Language extension status bar item shows a perpetual loading/spinning indicator. [Attach screenshot or AL output channel log here.]

5. Versions:

  • AL Language: 17.0.2273547
  • Visual Studio Code: 1.127.0 (x64)
  • Business Central Version: 28.1
  • List of Visual Studio Code extensions installed:
    • ms-dynamics-smb.al@17.0.2273547
  • Operating System:
    • Windows
    • Linux
    • MacOS
Final Checklist
  • 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#642076

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

Start by reproducing the issue with the documented multi-root .code-workspace and inspect the AL output channel and status bar behavior during project discovery. Compare the documentation-only root with the sibling AL repository containing the three nested projects. Done means loading completes and IntelliSense, diagnostics, and CodeLens work for all three AL projects.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.