Description
Custom APIs displayed in the VS Code API browser do not include the organization prefix. This affects any custom API sourced from the SCAPI schemas.
Expected Behavior
Custom APIs should display with their organization prefix (e.g., /organizations/{organizationId}/...) to match the actual endpoint paths.
Actual Behavior
Custom APIs are shown without the organization prefix, which is incorrect and could lead to confusion when developers reference these endpoints.
Notes
Custom APIs from the SCAPI schemas need special handling to include the organization prefix, as they differ from standard APIs in their path structure.
Affected Component
packages/b2c-vs-extension — API Browser feature
Description
Custom APIs displayed in the VS Code API browser do not include the organization prefix. This affects any custom API sourced from the SCAPI schemas.
Expected Behavior
Custom APIs should display with their organization prefix (e.g.,
/organizations/{organizationId}/...) to match the actual endpoint paths.Actual Behavior
Custom APIs are shown without the organization prefix, which is incorrect and could lead to confusion when developers reference these endpoints.
Notes
Custom APIs from the SCAPI schemas need special handling to include the organization prefix, as they differ from standard APIs in their path structure.
Affected Component
packages/b2c-vs-extension— API Browser feature