Skip to content

feat(apex-oas): defer activation until commands run - W-22168691#7351

Open
mshanemc wants to merge 24 commits into
developfrom
sm/W-22168691-defer-apex-oas-activation
Open

feat(apex-oas): defer activation until commands run - W-22168691#7351
mshanemc wants to merge 24 commits into
developfrom
sm/W-22168691-defer-apex-oas-activation

Conversation

@mshanemc

Copy link
Copy Markdown
Contributor

What does this PR do?

  • Defer salesforcedx-vscode-apex-oas activation until its commands run; no eager activation on project open. See contributing/decisions/activationEvents.md.
  • Refactor OAS pipeline to Effect (orchestrator, processor steps, strategies); drop barrels, enums, unused schema prop, beta path.
  • Move OAS e2e tests from salesforcedx-vscode-apex-replay-debugger-e2e Mocha suite to Playwright .headless.spec.ts in salesforcedx-vscode-apex-oas; add apexOasE2E.yml workflow.
  • Telemetry via OTEL annotateRootSpan (new effect-ext-utils helper); replace ad-hoc generation interaction logger.
  • Spectral error handling cleanup; reconcile/property-correction/reorder/validation step refactors.

What issues does this PR fix or reference?

@W-22168691@

@mshanemc mshanemc requested a review from a team as a code owner May 27, 2026 15:31
@mshanemc mshanemc requested review from daphne-sfdc and diyer and removed request for diyer May 27, 2026 15:31
mshanemc and others added 7 commits May 27, 2026 10:43
E2E_FROM_VSIX=1 requires .vsix files; vscode:bundle only produces dist/.
…r-apex-oas-activation

# Conflicts:
#	packages/playwright-vscode-ext/src/utils/helpers.ts
# Conflicts:
#	.vscode/cspell.json
#	packages/salesforcedx-vscode-apex-oas/src/apexExtensionUtils.ts
#	packages/salesforcedx-vscode-apex-oas/src/commands/createApexAction.ts
#	packages/salesforcedx-vscode-apex-oas/src/commands/index.ts
#	packages/salesforcedx-vscode-apex-oas/src/coreExtensionUtils.ts
#	packages/salesforcedx-vscode-apex-oas/src/oas/documentProcessorPipeline/betaInfoInjectionStep.ts
#	packages/salesforcedx-vscode-apex-oas/src/oas/documentProcessorPipeline/pipeline.ts
#	packages/salesforcedx-vscode-apex-oas/src/oas/externalServiceRegistrationManager.ts
#	packages/salesforcedx-vscode-apex-oas/src/oas/generationInteractionLogger.ts
#	packages/salesforcedx-vscode-apex-oas/src/oas/generationStrategy/openapi3.schema.ts
#	packages/salesforcedx-vscode-apex-oas/src/telemetry/index.ts
#	packages/salesforcedx-vscode-apex-oas/test/jest/index.test.ts
#	packages/salesforcedx-vscode-automation-tests/test/specs/createOasDoc.e2e.ts
#	packages/salesforcedx-vscode-automation-tests/test/testData/oasDocs.ts
#	packages/salesforcedx-vscode-automation-tests/test/utils/sampleClassData.ts
…r-apex-oas-activation

# Conflicts:
#	packages/effect-ext-utils/src/utils.ts
#	packages/playwright-vscode-ext/src/utils/helpers.ts
#	packages/salesforcedx-utils-vscode/src/index.ts
#	packages/salesforcedx-vscode-core/src/commands/util/lwcAuraDuplicateComponentCheckers.ts
… W-22168691

The bundled salesforcedx-einstein-gpt (A4V) extension checks the
EGPT-for-developers entitlement on default-org change by fetching a JWT.
E2E scratch orgs lack that entitlement, so the check fails and the
extension logs JWT errors. These are benign — OAS generation doesn't
depend on EGPT — but validateNoCriticalErrors flagged them, failing
the OAS desktop specs deterministically on macOS and ubuntu.

Add three patterns to NON_CRITICAL_ERROR_PATTERNS to cover the JWT
creation failure, the A4V activation-error wrapper, and the user-facing
UnknownJwtError message (apostrophe-agnostic substring, since the log
uses a curly apostrophe).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…r-apex-oas-activation

# Conflicts:
#	packages/playwright-vscode-ext/src/utils/helpers.ts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant