Overview - Ping-javascript-sdk

ping-javascript-sdk

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
525
35c4ad7f feat(oidc): refactor-wellknown-architecture refactor well known after discussion SDKS-4665
2 months ago by ryanbas21
Succeeded
525
ef7c96ee feat(oidc): refactor-wellknown-architecture refactor well known after discussion SDKS-4665
2 months ago by ryanbas21
Succeeded
525
c056c6a7 feat(oidc): refactor-wellknown-architecture refactor well known after discussion SDKS-4665
2 months ago by ryanbas21
Succeeded
525
9a8ca14e feat(journey-client): wellknown-endpoint-config-support Re-implement well known configuration and abstract into reusable package - Remove internal re-export file (wellknown.api.ts) - Import directly from source packages in internal modules - Keep consumer-facing exports in types.ts as the single public API - Add IPv6 localhost comment explaining design decision - Remove redundant inline comments (JSDoc is sufficient) Add framework-agnostic wellknown configuration fetching to sdk-oidc, following the architectural principle that sdk-effects packages are pure building blocks while *-client packages own RTK integration. Changes: - Add pure fetchWellknownConfiguration() effect to sdk-oidc - Create local wellknown.api.ts in journey-client, davinci-client - Update oidc-client with its own wellknown RTK integration - Each client wraps the pure effect in RTK Query BaseQueryFn - Fix vitest/@effect/vitest version compatibility (vitest ^3.2.0) - Fix MockInstance type for vitest 3.x compatibility Architecture: - sdk-effects/oidc: Pure async functions, no framework deps - *-client packages: Wrap effects in RTK Query BaseQueryFn
2 months ago by ryanbas21
Succeeded
525
f99b7d6c feat(journey-client): wellknown-endpoint-config-support Re-implement well known configuration and abstract into reusable package - Remove internal re-export file (wellknown.api.ts) - Import directly from source packages in internal modules - Keep consumer-facing exports in types.ts as the single public API - Add IPv6 localhost comment explaining design decision - Remove redundant inline comments (JSDoc is sufficient) Add framework-agnostic wellknown configuration fetching to sdk-oidc, following the architectural principle that sdk-effects packages are pure building blocks while *-client packages own RTK integration. Changes: - Add pure fetchWellknownConfiguration() effect to sdk-oidc - Create local wellknown.api.ts in journey-client, davinci-client - Update oidc-client with its own wellknown RTK integration - Each client wraps the pure effect in RTK Query BaseQueryFn - Fix vitest/@effect/vitest version compatibility (vitest ^3.2.0) - Fix MockInstance type for vitest 3.x compatibility Architecture: - sdk-effects/oidc: Pure async functions, no framework deps - *-client packages: Wrap effects in RTK Query BaseQueryFn
2 months ago by ryanbas21
Succeeded
525
28bf4582 feat(journey-client): wellknown-endpoint-config-support Re-implement well known configuration and abstract into reusable package - Remove internal re-export file (wellknown.api.ts) - Import directly from source packages in internal modules - Keep consumer-facing exports in types.ts as the single public API - Add IPv6 localhost comment explaining design decision - Remove redundant inline comments (JSDoc is sufficient) Add framework-agnostic wellknown configuration fetching to sdk-oidc, following the architectural principle that sdk-effects packages are pure building blocks while *-client packages own RTK integration. Changes: - Add pure fetchWellknownConfiguration() effect to sdk-oidc - Create local wellknown.api.ts in journey-client, davinci-client - Update oidc-client with its own wellknown RTK integration - Each client wraps the pure effect in RTK Query BaseQueryFn - Fix vitest/@effect/vitest version compatibility (vitest ^3.2.0) - Fix MockInstance type for vitest 3.x compatibility Architecture: - sdk-effects/oidc: Pure async functions, no framework deps - *-client packages: Wrap effects in RTK Query BaseQueryFn
2 months ago by ryanbas21
Failed
525
Fix ready→
af413647 feat(journey-client): wellknown-endpoint-config-support Re-implement well known configuration and abstract into reusable package - Remove internal re-export file (wellknown.api.ts) - Import directly from source packages in internal modules - Keep consumer-facing exports in types.ts as the single public API - Add IPv6 localhost comment explaining design decision - Remove redundant inline comments (JSDoc is sufficient) Add framework-agnostic wellknown configuration fetching to sdk-oidc, following the architectural principle that sdk-effects packages are pure building blocks while *-client packages own RTK integration. Changes: - Add pure fetchWellknownConfiguration() effect to sdk-oidc - Create local wellknown.api.ts in journey-client, davinci-client - Update oidc-client with its own wellknown RTK integration - Each client wraps the pure effect in RTK Query BaseQueryFn - Fix vitest/@effect/vitest version compatibility (vitest ^3.2.0) - Fix MockInstance type for vitest 3.x compatibility Architecture: - sdk-effects/oidc: Pure async functions, no framework deps - *-client packages: Wrap effects in RTK Query BaseQueryFn
2 months ago by ryanbas21
Succeeded
525
cff5145d feat(sdk-oidc): add pure fetchWellknownConfiguration effect Add framework-agnostic wellknown configuration fetching to sdk-oidc, following the architectural principle that sdk-effects packages are pure building blocks while *-client packages own RTK integration. Changes: - Add pure fetchWellknownConfiguration() effect to sdk-oidc - Create local wellknown.api.ts in journey-client, davinci-client - Update oidc-client with its own wellknown RTK integration - Each client wraps the pure effect in RTK Query BaseQueryFn - Fix vitest/@effect/vitest version compatibility (vitest ^3.2.0) - Fix MockInstance type for vitest 3.x compatibility Architecture: - sdk-effects/oidc: Pure async functions, no framework deps - *-client packages: Wrap effects in RTK Query BaseQueryFn
2 months ago by ryanbas21
Failed
525
Fix ready→
bcd89aa7 feat(sdk-oidc): add pure fetchWellknownConfiguration effect Add framework-agnostic wellknown configuration fetching to sdk-oidc, following the architectural principle that sdk-effects packages are pure building blocks while *-client packages own RTK integration. Changes: - Add pure fetchWellknownConfiguration() effect to sdk-oidc - Create local wellknown.api.ts in journey-client, davinci-client - Update oidc-client with its own wellknown RTK integration - Each client wraps the pure effect in RTK Query BaseQueryFn - Fix vitest/@effect/vitest version compatibility (vitest ^3.2.0) - Fix MockInstance type for vitest 3.x compatibility Architecture: - sdk-effects/oidc: Pure async functions, no framework deps - *-client packages: Wrap effects in RTK Query BaseQueryFn
2 months ago by ryanbas21
Failed
525
986da1a7 feat(sdk-oidc): add pure fetchWellknownConfiguration effect Add framework-agnostic wellknown configuration fetching to sdk-oidc, following the architectural principle that sdk-effects packages are pure building blocks while *-client packages own RTK integration. Changes: - Add pure fetchWellknownConfiguration() effect to sdk-oidc - Create local wellknown.api.ts in journey-client, davinci-client - Update oidc-client with its own wellknown RTK integration - Each client wraps the pure effect in RTK Query BaseQueryFn - Fix vitest/@effect/vitest version compatibility (vitest ^3.2.0) - Fix MockInstance type for vitest 3.x compatibility Architecture: - sdk-effects/oidc: Pure async functions, no framework deps - *-client packages: Wrap effects in RTK Query BaseQueryFn
2 months ago by ryanbas21
Failed
525
072a55ea feat(journey-client): wellknown-endpoint-config-support Re-implement well known configuration and abstract into reusable package - Remove internal re-export file (wellknown.api.ts) - Import directly from source packages in internal modules - Keep consumer-facing exports in types.ts as the single public API - Add IPv6 localhost comment explaining design decision - Remove redundant inline comments (JSDoc is sufficient) [Self-Healing CI Rerun]
2 months ago by nx-cloud[bot]
Failed
525
Flaky task→
60cd9a0a feat(journey-client): wellknown-endpoint-config-support Re-implement well known configuration and abstract into reusable package - Remove internal re-export file (wellknown.api.ts) - Import directly from source packages in internal modules - Keep consumer-facing exports in types.ts as the single public API - Add IPv6 localhost comment explaining design decision - Remove redundant inline comments (JSDoc is sufficient)
2 months ago by ryanbas21
Failed
525
5a5a98aa fix!: update-error-handling-across-packages
2 months ago by ryanbas21
Succeeded
525
8b88793b chore: remove-wellknown.api-file
2 months ago by ryanbas21
Succeeded
525
8ffc980f chore: coderabbit-comments
2 months ago by ryanbas21
Succeeded
525
95eee18e chore: more-refactoring-rebase-with-main
2 months ago by ryanbas21
Succeeded
525
03b785b6 chore: move-to-wellknown-refactor
2 months ago by ryanbas21
Failed
525
Fix ready→
03b785b6 chore: move-to-wellknown-refactor
2 months ago by ryanbas21
Succeeded
525
73386a29 feat(journey-client): wellknown-endpoint-config-support
2 months ago by ryanbas21