Skip to content

feat(pm-wizard): drive mutation auth from provider metadata#1318

Merged
aaight merged 1 commit into
devfrom
feature/pm-wizard-metadata-auth
May 10, 2026
Merged

feat(pm-wizard): drive mutation auth from provider metadata#1318
aaight merged 1 commit into
devfrom
feature/pm-wizard-metadata-auth

Conversation

@aaight
Copy link
Copy Markdown
Collaborator

@aaight aaight commented May 10, 2026

Summary

Implements metadata-driven auth for PM wizard mutation helpers.

Card: https://trello.com/c/6a004e0e420dd9f9ea6a32f9

Changes

  • Pass the active provider wizard id and auth metadata through ProviderHooksContext so provider hook modules no longer hard-code their own mutation auth metadata.
  • Add metadata-driven request builders for provider label creation and custom-field creation, both using buildProviderAuthArgFromMetadata.
  • Update Trello, Linear, and JIRA provider hook wiring to receive provider ID/auth from the manifest context.
  • Extend pm-wizard-hooks unit coverage for raw credential payloads, stored credential { projectId } fallback, and missing-credential errors across Trello, JIRA, and Linear mutation flows.

Verification

  • npx vitest run --project unit-core tests/unit/web/pm-wizard-hooks.test.ts
  • npm run lint:fix
  • npm run lint (passes with existing warnings)
  • npm run typecheck
  • npm test
  • npm run test:integration

Notes

npm run lint still reports existing warning-level findings in unrelated files; it exits successfully with no errors.

🕵️ codex · gpt-5.5 · run details

Copy link
Copy Markdown
Collaborator

@nhopeatall nhopeatall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - the mutation request builders now use manifest auth metadata, provider hooks receive the active manifest id/auth from context, and the targeted pm-wizard-hooks unit suite passes locally.

🕵️ codex · gpt-5.5 · run details

@aaight aaight merged commit a767abc into dev May 10, 2026
9 checks passed
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.

2 participants