BC Observatoryunofficial, made by waldo
codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 8334 "VS Code Integration"

System Application · System.Integration

Open in Claude8334.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC263 procedures added
  4. BC27-30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 8333 "VS Code Integration Impl." (calls, 6 links)VS Code Integration Impl.Codeunit 5378 "Page Inspection VS Code Helper" (calls, 3 links)Page Inspection VS Code Helper

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

System Application · System.Integration · BC25-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Public

Procedures

  • OpenExtensionSourceInVSCode(var PublishedApplication: Record "Published Application"): Opens an URL that sends a request to VS Code to retrieve and open the source code of the provided extension from Git.
  • UpdateConfigurationsInVSCode() + BC26: Opens an URL that sends a request to VS Code to update the launch configurations to match the current environment to publish and debug.
  • UpdateDependenciesInVSCode(var PublishedApplication: Record "Published Application") + BC26: Opens an URL that sends a request to VS Code to add and download the selected extensions as dependencies.
  • GetDependenciesAsJson(var PublishedApplication: Record "Published Application"): Text + BC26: Returns the selected extensions as a JSON array of dependencies.
  • NavigateToPageDefinitionInVSCode(var PageInfoAndFields: Record "Page Info And Fields"; var NavAppInstalledApp: Record "NAV App Installed App"): Opens an URL that sends a request to VS Code to navigate to the source definition of the given page and to download the dependent symbols.
  • NavigateFieldDefinitionInVSCode(var PageInfoAndFields: Record "Page Info And Fields"; var NavAppInstalledApp: Record "NAV App Installed App"): Opens an URL that sends a request to VS Code to navigate to the source definition of the given table field and to download the dependent symbols.

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

  • Codeunit 8333 “VS Code Integration Impl.” (6 calls: GetDependenciesAsJson → GetDependenciesAsSerializedJsonArray, NavigateFieldDefinitionInVSCode → NavigateToObjectDefinitionInVSCode, NavigateToPageDefinitionInVSCode → NavigateToObjectDefinitionInVSCode, …)

Called by

  • Codeunit 5378 “Page Inspection VS Code Helper” (3 calls: NavigateFieldDefinitionInVSCode → NavigateFieldDefinitionInVSCode, NavigateToPageDefinitionInVSCode → NavigateToPageDefinitionInVSCode, OpenExtensionSourceInVSCode → OpenExtensionSourceInVSCode)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "VS Code Integration"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources