feat(davinci-client): add fido2 collectors #428
Conversation
🦋 Changeset detectedLatest commit: 1a29b13 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
WalkthroughAdds FIDO2 (WebAuthn) collectors, input/value types, and factory helpers; expands AutoCollector unions and inference; makes validation.input nullable; extends update/validate flows and runtime reducer handling to accept FIDO2 object-value collectors; updates utilities, types, and tests across the davinci-client package. (34 words) Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor User
participant UI as Form UI
participant Reducer as node.reducer
participant Utils as collector.utils
participant Store as client.store
Note over UI,Reducer: node/next constructs collectors (includes FIDO collectors)
UI->>Reducer: node/next (fields incl. FIDO)
Reducer->>Utils: returnFidoRegistrationCollector / returnFidoAuthenticationCollector
Utils-->>Reducer: ObjectValueAutoCollector / SingleValueAutoCollector
Reducer-->>UI: state updated with collectors
Note over User,UI: User performs WebAuthn (attestation/assertion)
User->>UI: FIDO response
UI->>Reducer: node/update (collectorId, value)
Reducer->>Store: validate(collector: AutoCollectors)
Store-->>Reducer: validation result
alt validation ok
Reducer->>Reducer: assign FIDO input value to collector.input.value
Reducer-->>UI: updated state/result
else validation error
Store-->>UI: validation error
end
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
View your CI Pipeline Execution ↗ for commit 1a29b13
☁️ Nx Cloud last updated this comment at |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #428 +/- ##
===========================================
+ Coverage 18.75% 52.07% +33.32%
===========================================
Files 138 19 -119
Lines 27368 1761 -25607
Branches 951 254 -697
===========================================
- Hits 5132 917 -4215
+ Misses 22236 844 -21392
🚀 New features to boost your workflow:
|
@forgerock/davinci-client
@forgerock/oidc-client
@forgerock/protect
@forgerock/sdk-types
@forgerock/sdk-utilities
@forgerock/iframe-manager
@forgerock/sdk-logger
@forgerock/sdk-oidc
@forgerock/sdk-request-middleware
@forgerock/storage
commit: |
|
Deployed ab94e1d to https://ForgeRock.github.io/ping-javascript-sdk/pr-428/ab94e1d5c7b2199b36d6d8b25d5aa60af63c3f3c branch gh-pages in ForgeRock/ping-javascript-sdk |
📦 Bundle Size Analysis📦 Bundle Size Analysis🆕 New Packages🆕 @forgerock/device-client - 9.2 KB (new) 13 packages analyzed • Baseline from latest Legend🆕 New package ℹ️ How bundle sizes are calculated
🔄 Updated automatically on each push to this PR |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/davinci-client/src/lib/client.store.ts (1)
236-289: Allow AutoCollector updates with FIDO2 payloads.
returnAutoCollectornow emits FIDO2 collectors whoseinput.valueis aFido2RegistrationInputValue/Fido2AuthenticationInputValue, but the updater here still only acceptsstring | string[] | PhoneNumberInputValue. As a result,update(fidoCollector)(attestationPayload)no longer type-checks even though that payload is required for the new collectors. Please widen the accepted value union (and theUpdatertype inclient.types.ts) to include the FIDO2 input interfaces so the feature is actually usable without unsafe casts.-import type { - SingleValueCollectors, - MultiSelectCollector, - ObjectValueCollectors, - PhoneNumberInputValue, - AutoCollectors, - MultiValueCollectors, -} from './collector.types.js'; +import type { + SingleValueCollectors, + MultiSelectCollector, + ObjectValueCollectors, + PhoneNumberInputValue, + AutoCollectors, + MultiValueCollectors, + Fido2RegistrationInputValue, + Fido2AuthenticationInputValue, +} from './collector.types.js'; @@ - return function (value: string | string[] | PhoneNumberInputValue, index?: number) { + return function ( + value: + | string + | string[] + | PhoneNumberInputValue + | Fido2RegistrationInputValue + | Fido2AuthenticationInputValue, + index?: number, + ) {
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (9)
packages/davinci-client/src/lib/client.store.ts(2 hunks)packages/davinci-client/src/lib/collector.types.ts(5 hunks)packages/davinci-client/src/lib/collector.utils.test.ts(3 hunks)packages/davinci-client/src/lib/collector.utils.ts(9 hunks)packages/davinci-client/src/lib/davinci.types.ts(3 hunks)packages/davinci-client/src/lib/davinci.utils.ts(2 hunks)packages/davinci-client/src/lib/node.reducer.ts(8 hunks)packages/davinci-client/src/lib/node.types.test-d.ts(2 hunks)packages/davinci-client/src/lib/node.types.ts(2 hunks)
🧰 Additional context used
🧬 Code graph analysis (8)
packages/davinci-client/src/lib/node.types.test-d.ts (1)
packages/davinci-client/src/lib/collector.types.ts (2)
Fido2RegistrationCollector(601-605)Fido2AuthenticationCollector(606-610)
packages/davinci-client/src/lib/client.store.ts (2)
packages/davinci-client/src/lib/collector.types.ts (4)
SingleValueCollectors(174-179)ObjectValueCollectors(415-420)MultiValueCollectors(250-252)AutoCollectors(617-621)packages/davinci-client/src/lib/client.store.utils.ts (1)
handleUpdateValidateError(51-66)
packages/davinci-client/src/lib/davinci.utils.ts (1)
packages/davinci-client/src/lib/collector.types.ts (3)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-316)Fido2AuthenticationInputValue(318-330)
packages/davinci-client/src/lib/node.types.ts (1)
packages/davinci-client/src/lib/collector.types.ts (2)
Fido2RegistrationCollector(601-605)Fido2AuthenticationCollector(606-610)
packages/davinci-client/src/lib/collector.utils.test.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)ProtectField(156-161)packages/davinci-client/src/lib/collector.utils.ts (1)
returnAutoCollector(272-385)
packages/davinci-client/src/lib/collector.utils.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.types.ts (6)
AutoCollectorTypes(567-571)InferAutoCollectorType(630-640)ValidatedTextCollector(184-184)ObjectValueCollectors(415-420)MultiValueCollectors(250-252)AutoCollectors(617-621)
packages/davinci-client/src/lib/collector.types.ts (1)
packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)
packages/davinci-client/src/lib/node.reducer.ts (2)
packages/davinci-client/src/lib/collector.types.ts (5)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-316)Fido2AuthenticationInputValue(318-330)Fido2RegistrationCollector(601-605)Fido2AuthenticationCollector(606-610)packages/davinci-client/src/lib/collector.utils.ts (3)
returnProtectCollector(423-425)returnFido2RegistrationCollector(433-435)returnFido2AuthenticationCollector(443-445)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: pr
- GitHub Check: Mend Code Security Check
ancheetah
force-pushed
the
SDKS-4372-webauthn-collectors
branch
from
d2c6b35 to
33ad81a
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (2)
packages/davinci-client/src/lib/davinci.types.ts (2)
163-191: Export the FIDO2 option interfaces.
Fido2RegistrationOptions(line 163) andFido2AuthenticationOptions(line 183) are used in exported field types but are not themselves exported. TypeScript will emitTS4058during declaration generation because exported members reference private names.Apply this diff to export both interfaces:
-interface Fido2RegistrationOptions +export interface Fido2RegistrationOptions extends Omit<PublicKeyCredentialCreationOptions, 'challenge' | 'user'> { ... -interface Fido2AuthenticationOptions +export interface Fido2AuthenticationOptions extends Omit<PublicKeyCredentialRequestOptions, 'challenge' | 'allowCredentials'> {
186-190: FixallowCredentialsto be an array.The
allowCredentialsproperty is typed as a single object (lines 186-190), but the WebAuthn spec defines it asPublicKeyCredentialDescriptor[]. This breaks type compatibility and will cause runtime issues when multiple credentials are allowed.Apply this diff to correct the type:
allowCredentials?: { id: number[]; transports?: AuthenticatorTransport[]; type: PublicKeyCredentialType; - }; + }[];
🧹 Nitpick comments (1)
packages/davinci-client/src/lib/node.reducer.ts (1)
182-189: Add explicit return or break to prevent fall-through.The FIDO2 case branches (lines 183-187) don't explicitly return or break, allowing fall-through to line 190 if neither credential option is present. While the
breakon line 188 prevents fall-through to the next case, the logic would be clearer with explicit returns in each branch.Consider this refactor for clarity:
case 'FIDO2': { if ('publicKeyCredentialCreationOptions' in field) { - return returnFido2RegistrationCollector(field, idx); + return returnFido2RegistrationCollector(field, idx); } else if ('publicKeyCredentialRequestOptions' in field) { - return returnFido2AuthenticationCollector(field, idx); + return returnFido2AuthenticationCollector(field, idx); } + // Fall through to default handling if neither option is present break; }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (9)
packages/davinci-client/src/lib/client.store.ts(2 hunks)packages/davinci-client/src/lib/collector.types.ts(5 hunks)packages/davinci-client/src/lib/collector.utils.test.ts(3 hunks)packages/davinci-client/src/lib/collector.utils.ts(9 hunks)packages/davinci-client/src/lib/davinci.types.ts(3 hunks)packages/davinci-client/src/lib/davinci.utils.ts(2 hunks)packages/davinci-client/src/lib/node.reducer.ts(8 hunks)packages/davinci-client/src/lib/node.types.test-d.ts(2 hunks)packages/davinci-client/src/lib/node.types.ts(2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- packages/davinci-client/src/lib/node.types.test-d.ts
- packages/davinci-client/src/lib/davinci.utils.ts
🧰 Additional context used
🧬 Code graph analysis (6)
packages/davinci-client/src/lib/collector.utils.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.types.ts (6)
AutoCollectorTypes(548-552)InferAutoCollectorType(611-621)ValidatedTextCollector(184-184)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(598-602)
packages/davinci-client/src/lib/collector.types.ts (1)
packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)
packages/davinci-client/src/lib/node.reducer.ts (2)
packages/davinci-client/src/lib/collector.types.ts (5)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-307)Fido2AuthenticationInputValue(309-311)Fido2RegistrationCollector(582-586)Fido2AuthenticationCollector(587-591)packages/davinci-client/src/lib/collector.utils.ts (3)
returnProtectCollector(423-425)returnFido2RegistrationCollector(433-435)returnFido2AuthenticationCollector(443-445)
packages/davinci-client/src/lib/node.types.ts (1)
packages/davinci-client/src/lib/collector.types.ts (2)
Fido2RegistrationCollector(582-586)Fido2AuthenticationCollector(587-591)
packages/davinci-client/src/lib/client.store.ts (2)
packages/davinci-client/src/lib/collector.types.ts (4)
SingleValueCollectors(174-179)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(598-602)packages/davinci-client/src/lib/client.store.utils.ts (1)
handleUpdateValidateError(51-66)
packages/davinci-client/src/lib/collector.utils.test.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)ProtectField(156-161)packages/davinci-client/src/lib/collector.utils.ts (1)
returnAutoCollector(272-385)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Mend Code Security Check
- GitHub Check: pr
🔇 Additional comments (11)
packages/davinci-client/src/lib/collector.utils.test.ts (2)
806-957: LGTM!The new
returnAutoCollectortests comprehensively validate the FIDO2 registration, authentication, and Protect collector structures. Each test correctly verifies input/output shapes, config mappings, and validation rules.
995-995: LGTM!Correctly updated to test an empty array instead of an empty object, aligning with the multi-value collector's array-based validation logic.
packages/davinci-client/src/lib/client.store.ts (1)
294-348: LGTM!The
validatemethod correctly extends support toAutoCollectors, including the new FIDO2 collectors. The category check properly includesSingleValueAutoCollector, and the JSDoc is appropriately updated.packages/davinci-client/src/lib/node.types.ts (1)
26-48: LGTM!The FIDO2 collector types are correctly imported and added to the public
Collectorsunion, extending the type system to support WebAuthn flows.packages/davinci-client/src/lib/node.reducer.ts (2)
300-324: LGTM!The FIDO2 collector update handling correctly validates input types and required properties (
attestationValuefor registration,assertionValuefor authentication) before updating collector values. The logic follows the established pattern used for other object-value collectors.
225-235: LGTM!The refinement from
SingleValueAutoCollectortoProtectCollector(line 228) provides more specific type checking while maintaining the string value validation. This aligns with the expanded auto-collector type system.packages/davinci-client/src/lib/collector.types.ts (1)
305-621: LGTM!The type system extensions for FIDO2 support are well-structured:
- New input value interfaces properly use
PublicKeyCredentialfrom the WebAuthn API- The
AutoCollectorgeneric is enhanced withIVfor clarity and optional validation- New collector types (
Fido2RegistrationCollector,Fido2AuthenticationCollector) correctly extend the base- Union types and inference mappings are complete and consistent
packages/davinci-client/src/lib/collector.utils.ts (4)
272-291: LGTM!The refactoring to remove the
dataparameter and construct the validation array upfront is cleaner and more maintainable. The validation logic correctly handles therequiredproperty common to FIDO2 fields.
314-365: LGTM!The FIDO2 collector branches are well-implemented:
- Proper discrimination based on credential options properties
- Config correctly captures
publicKeyCredentialCreationOptions/publicKeyCredentialRequestOptions,action, andtrigger- Input value initialized to
{}for object-based WebAuthn credentials- Validation array conditionally included based on content
423-445: LGTM!The wrapper functions follow the established pattern and correctly delegate to
returnAutoCollectorwith the appropriate collector type. The removal of thedataparameter fromreturnProtectCollectoraligns with the signature changes.
705-709: LGTM!The
returnValidatorsignature correctly extends to includeAutoCollectors, and the return type change fromRecord<string, string>toRecord<string, unknown>properly accommodates object-based input values used by FIDO2 collectors.
There was a problem hiding this comment.
I feel like we should start splitting these files up that are getting pretty long. Maybe split by category of collector? Thoughts?
There was a problem hiding this comment.
Same goes for the accompanying unit test file... it's very long. We could have a /collectors folder which hosts the utils and types. Break down by category as you suggested. The types could also probably be broken down by category. Question is do we want to do this refactoring now or save it for later?
There was a problem hiding this comment.
I'll leave this up to you. If you have bigger fish to fry, then we can do it later. I just thought I'd bring it up as I always get squeamish with long running files like this :)
There was a problem hiding this comment.
Will save this for the end of the sprint if there's time
There was a problem hiding this comment.
Sounds good. No rush. We can always just put a tech debt story in the backlog as well.
| key: field.key, | ||
| value: {}, | ||
| type: field.type, | ||
| validation: validationArray.length ? validationArray : undefined, |
There was a problem hiding this comment.
Can we use null instead of undefined?
There was a problem hiding this comment.
I gave null a try for the ObjectValueAutoCollectors. Let me know if you like it better. As code rabbit pointed out below, we'll have to update our other validator props in other collectors to be more consistent.
| return returnProtectCollector(field, idx); | ||
| } | ||
| case 'FIDO2': { | ||
| if ('publicKeyCredentialCreationOptions' in field) { |
There was a problem hiding this comment.
Rather than going off of a property's presence, would it be easier to use the action property's value: "REGISTER" or "AUTHENTICATE"?
There was a problem hiding this comment.
That's a good idea. I assume we are always guaranteed these values and it's not something user-configured?
There was a problem hiding this comment.
You're assumption is correct. These properties should not change, as it's a part of the API. I only suggest using the action property as it's a bit more concise and "self-documenting".
| 'publicKeyCredentialCreationOptions' in field | ||
| ) { | ||
| return { | ||
| category: 'SingleValueAutoCollector', |
There was a problem hiding this comment.
I think we should have a different category for this. SingleValue doesn't feel all that accurate. It's more of an ObjectValue, like device or phone number collectors, as opposed to Protect, which is just a string value, yeah? So, ObjectValueAutoCollector?
| input: { | ||
| key: field.key, | ||
| value: data || '', | ||
| value: '', |
There was a problem hiding this comment.
Yes, from my understanding this data passed in here comes from formData on the DaVinci response (which is typically prefilled data). Neither WebAuthn or Protect come with prefilled data as far as I know so I think it's ok to remove this.
| collector.category === 'SingleValueCollector' || | ||
| collector.category === 'ValidatedSingleValueCollector' || | ||
| collector.category === 'SingleValueAutoCollector' | ||
| collector.type === 'ProtectCollector' |
There was a problem hiding this comment.
If we change the category of the FIDO2 collectors to ObjectValueAutoCollectors, then we could potentially not need this change.
There was a problem hiding this comment.
I thought about this too. I'll go ahead and make that change to the category
ancheetah
force-pushed
the
SDKS-4372-webauthn-collectors
branch
from
33ad81a to
fe032c0
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
packages/davinci-client/src/lib/node.reducer.ts (1)
300-324: Consider consolidating duplicate FIDO2 validation logic.The validation blocks for
Fido2RegistrationCollector(lines 300-311) andFido2AuthenticationCollector(lines 313-324) are nearly identical, differing only in the property name check (attestationValuevsassertionValue). This duplication could be reduced with a helper function or consolidated logic.Example refactor to reduce duplication:
+ const isFido2Collector = + collector.type === 'Fido2RegistrationCollector' || + collector.type === 'Fido2AuthenticationCollector'; + + if (isFido2Collector) { - if (collector.type === 'Fido2RegistrationCollector') { if (typeof action.payload.id !== 'string') { throw new Error('Index argument must be a string'); } if (typeof action.payload.value !== 'object') { throw new Error('Value argument must be an object'); } - if (!('attestationValue' in action.payload.value)) { - throw new Error('Value argument must contain an attestationValue property'); + const requiredProp = collector.type === 'Fido2RegistrationCollector' + ? 'attestationValue' + : 'assertionValue'; + if (!(requiredProp in action.payload.value)) { + throw new Error(`Value argument must contain a ${requiredProp} property`); } collector.input.value = action.payload.value; + return; } - - if (collector.type === 'Fido2AuthenticationCollector') { - if (typeof action.payload.id !== 'string') { - throw new Error('Index argument must be a string'); - } - if (typeof action.payload.value !== 'object') { - throw new Error('Value argument must be an object'); - } - if (!('assertionValue' in action.payload.value)) { - throw new Error('Value argument must contain an assertionValue property'); - } - collector.input.value = action.payload.value; - }packages/davinci-client/src/lib/collector.types.ts (1)
555-576: Unify handling of thevalidationfield. It’s currently declared asvalidation?: ValidationRequired[] | nullbut some code paths assignundefined(e.g. collector.utils.ts lines 523–527 and 650–654) while others usenull. Decide on a single “no validations” sentinel—eithernullorundefined—and update the interface and all assignments to match.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (10)
packages/davinci-client/src/lib/client.store.ts(4 hunks)packages/davinci-client/src/lib/collector.types.ts(5 hunks)packages/davinci-client/src/lib/collector.utils.test.ts(3 hunks)packages/davinci-client/src/lib/collector.utils.ts(9 hunks)packages/davinci-client/src/lib/davinci.types.ts(3 hunks)packages/davinci-client/src/lib/davinci.utils.ts(2 hunks)packages/davinci-client/src/lib/node.reducer.test.ts(2 hunks)packages/davinci-client/src/lib/node.reducer.ts(8 hunks)packages/davinci-client/src/lib/node.types.test-d.ts(2 hunks)packages/davinci-client/src/lib/node.types.ts(2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- packages/davinci-client/src/lib/node.types.test-d.ts
- packages/davinci-client/src/lib/davinci.utils.ts
🧰 Additional context used
🧬 Code graph analysis (7)
packages/davinci-client/src/lib/node.reducer.test.ts (4)
packages/davinci-client/src/lib/collector.types.ts (3)
ProtectCollector(578-582)Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)packages/davinci-client/src/lib/node.reducer.ts (1)
nodeCollectorReducer(107-326)packages/davinci-client/src/lib/davinci.types.ts (2)
Fido2RegistrationOptions(163-171)Fido2AuthenticationOptions(183-191)
packages/davinci-client/src/lib/node.types.ts (1)
packages/davinci-client/src/lib/collector.types.ts (2)
Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)
packages/davinci-client/src/lib/collector.utils.test.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.utils.ts (2)
returnSingleValueAutoCollector(273-324)returnObjectValueAutoCollector(333-419)
packages/davinci-client/src/lib/collector.utils.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.types.ts (7)
SingleValueAutoCollectorTypes(548-548)ObjectValueAutoCollectorTypes(549-552)InferAutoCollectorType(618-630)ValidatedTextCollector(184-184)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
packages/davinci-client/src/lib/node.reducer.ts (2)
packages/davinci-client/src/lib/collector.types.ts (5)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-307)Fido2AuthenticationInputValue(309-311)Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)packages/davinci-client/src/lib/collector.utils.ts (3)
returnProtectCollector(457-459)returnFido2RegistrationCollector(467-469)returnFido2AuthenticationCollector(477-479)
packages/davinci-client/src/lib/client.store.ts (2)
packages/davinci-client/src/lib/client.store.utils.ts (1)
handleUpdateValidateError(51-66)packages/davinci-client/src/lib/collector.types.ts (7)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-307)Fido2AuthenticationInputValue(309-311)SingleValueCollectors(174-179)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
packages/davinci-client/src/lib/collector.types.ts (1)
packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Mend Code Security Check
- GitHub Check: pr
🔇 Additional comments (6)
packages/davinci-client/src/lib/collector.types.ts (2)
305-311: LGTM! FIDO2 input value types are well-defined.The optional fields (
attestationValue?andassertionValue?) align with the WebAuthn API flow where these values are populated after the browser credential operation completes.
547-553: Good separation of auto collector categories.Splitting
SingleValueAutoCollectorTypesandObjectValueAutoCollectorTypesprovides clear type boundaries and makes the FIDO2 collectors (which handle complex objects) distinct from simple value collectors like Protect.packages/davinci-client/src/lib/node.reducer.ts (1)
182-189: LGTM! Action-based routing aligns with prior feedback.Using
field.actionto distinguish between REGISTER and AUTHENTICATE flows is more concise and self-documenting than checking for property presence.Based on learnings
packages/davinci-client/src/lib/collector.utils.ts (3)
326-419: LGTM! NewreturnObjectValueAutoCollectorfollows established patterns.The function correctly:
- Validates required field properties
- Builds validation arrays based on field requirements
- Distinguishes between FIDO2 registration and authentication via
field.action- Initializes
input.valueto an empty object{}(appropriate for FIDO2 flows)- Returns properly typed collectors
589-605: Good defensive programming with optional chaining.Adding optional chaining (
field.options?.) prevents potential runtime errors if the field structure is malformed or incomplete.Also applies to: 617-624
736-743: Ensure returnValidator handles FIDO2 object values
The ‘required’ rule counts object keys (e.g. attestationValue/assertionValue) but there are no tests exercising returnValidator for Fido2RegistrationCollector or Fido2AuthenticationCollector. Add or update validator tests to confirm FIDO2 inputs pass/ fail as intended.
| key: field.key, | ||
| value: {}, | ||
| type: field.type, | ||
| validation: validationArray.length ? validationArray : null, |
There was a problem hiding this comment.
Inconsistent validation assignment: null vs array length check.
Lines 365, 388, and 411 use validationArray.length ? validationArray : null, setting validation to null when empty. However, other collectors in this file (e.g., lines 525, 652) use undefined for empty validation. This inconsistency should be resolved.
Consider standardizing to undefined (or omitting the field entirely):
- validation: validationArray.length ? validationArray : null,
+ validation: validationArray.length ? validationArray : undefined,Or even better, only include validation when present:
input: {
key: field.key,
value: {},
type: field.type,
- validation: validationArray.length ? validationArray : null,
+ ...(validationArray.length && { validation: validationArray }),
},Also applies to: 388-388, 411-411
🤖 Prompt for AI Agents
In packages/davinci-client/src/lib/collector.utils.ts around lines 365, 388 and
411, the code sets validation to null when validationArray is empty (validation:
validationArray.length ? validationArray : null) which is inconsistent with
other collectors that use undefined; update these three locations to standardize
behavior by either (a) setting validation to undefined when empty (validation:
validationArray.length ? validationArray : undefined) or preferably (b) only
include the validation field when validationArray has items (i.e., conditionally
add the validation property to the returned object when validationArray.length >
0) so all collectors use the same undefined/omitted convention.
There was a problem hiding this comment.
Where are the other instances of undefined being assigned?
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Find all instances where validation is assigned in collector.utils.ts
rg -n "validation.*validationArray" packages/davinci-client/src/lib/collector.utils.ts
Length of output: 411
@cerebrl The other instances where undefined is assigned to validation are:
-
Line 525 - in
returnMultiValueCollector:validation: validationArray.length ? validationArray : undefined,
-
Line 652 - in
returnObjectCollector:validation: validationArray.length ? validationArray : undefined,
In contrast, the new returnObjectValueAutoCollector function uses null for validation on lines 365, 388, and 411. This creates an inconsistency with the existing pattern in the codebase where returnMultiValueCollector and returnObjectCollector both use undefined when the validation array is empty.
🧬 Code Graph Analysis Results
<no_relevant_code_snippets>
There was a problem hiding this comment.
Nice! This is actually helpful!
There was a problem hiding this comment.
@cerebrl You're welcome! I'm glad the analysis was helpful. Let me know if you need anything else as you work through the validation inconsistency. 😊
|
Added ObjectValueAutoCollector type and unit tests for AutoCollectors in the node reducer. |
| } | ||
|
|
||
| if (collectorType === 'ProtectCollector') { | ||
| if (collectorType === 'ProtectCollector' && field.type === 'PROTECT') { |
There was a problem hiding this comment.
Is this addition to the conditional still needed now that we've narrowed the AutoCollector types?
There was a problem hiding this comment.
good catch, no longer needed
| }); | ||
| } | ||
|
|
||
| if (collectorType === 'Fido2RegistrationCollector' && field.action === 'REGISTER') { |
There was a problem hiding this comment.
This isn't a big thing, but does the tested collectorType not narrow enough? It would be nice if the type being Fido2RegistrationCollector would be enough without the need of the added field.action === 'REGISTER'. This would make it consistent with the rest of this file's conditions.
There was a problem hiding this comment.
Narrowing on just collectorType is not enough because the field input is then left ambiguous and typescript will complain about the public key credential options.
If you take a look at returnObjectCollector we do something similar - narrow on field.type. In the case of FIDO2 the field.type is FIDO2 for both registration/authentication so we can't use that. It's actually enough to narrow if we just use field.action but it feels safer to explicitly have the collectorType conditional in case other field types have a similar action.
There was a problem hiding this comment.
I guess I misspoke. I should have asked if we can narrow on field.action alone? Does the collectorType matter in this sense? It doesn't seem to impact the logic at all.
There was a problem hiding this comment.
Yes, we can narrow on field.action alone. This would also remove the need for returning a generic ObjectValueAutoCollector at the end because at that point the field is of type never.
ancheetah
force-pushed
the
SDKS-4372-webauthn-collectors
branch
from
fe032c0 to
7471c5c
Compare
|
Updated validation types and narrowing on ObjectValueAutoCollectors. |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
packages/davinci-client/src/lib/node.reducer.test.ts (2)
925-1028: Consider typing the mock input value explicitly.The TODO comment on line 927 suggests explicitly typing
mockInputValueasFido2RegistrationInputValue. While the test works with the implicit typing, explicit typing would improve type safety and catch mismatches earlier.Apply this diff to add explicit typing:
- // todo: declare inputValue type as Fido2RegistrationInputValue - const mockInputValue = { + const mockInputValue: Fido2RegistrationInputValue = { attestationValue: {Otherwise, the test comprehensively validates the Fido2RegistrationCollector pathway with appropriate mock data structures.
1030-1117: Consider typing the mock input value explicitly.Similar to the registration test, the TODO comment on line 1032 suggests explicitly typing
mockInputValueasFido2AuthenticationInputValuefor improved type safety.Apply this diff to add explicit typing:
- // todo: declare inputValue type as Fido2AuthenticationInputValue - const mockInputValue = { + const mockInputValue: Fido2AuthenticationInputValue = { assertionValue: {The test otherwise provides excellent coverage of the Fido2AuthenticationCollector update pathway with realistic mock credentials and options.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (11)
packages/davinci-client/src/lib/client.store.ts(4 hunks)packages/davinci-client/src/lib/collector.types.test-d.ts(1 hunks)packages/davinci-client/src/lib/collector.types.ts(10 hunks)packages/davinci-client/src/lib/collector.utils.test.ts(8 hunks)packages/davinci-client/src/lib/collector.utils.ts(10 hunks)packages/davinci-client/src/lib/davinci.types.ts(3 hunks)packages/davinci-client/src/lib/davinci.utils.ts(2 hunks)packages/davinci-client/src/lib/node.reducer.test.ts(12 hunks)packages/davinci-client/src/lib/node.reducer.ts(8 hunks)packages/davinci-client/src/lib/node.types.test-d.ts(2 hunks)packages/davinci-client/src/lib/node.types.ts(2 hunks)
🚧 Files skipped from review as they are similar to previous changes (4)
- packages/davinci-client/src/lib/node.reducer.ts
- packages/davinci-client/src/lib/node.types.test-d.ts
- packages/davinci-client/src/lib/node.types.ts
- packages/davinci-client/src/lib/davinci.utils.ts
🧰 Additional context used
🧬 Code graph analysis (5)
packages/davinci-client/src/lib/collector.types.ts (1)
packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)
packages/davinci-client/src/lib/collector.utils.test.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.utils.ts (2)
returnSingleValueAutoCollector(273-324)returnObjectValueAutoCollector(333-401)
packages/davinci-client/src/lib/node.reducer.test.ts (4)
packages/davinci-client/src/lib/collector.types.ts (3)
ProtectCollector(578-582)Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)packages/davinci-client/src/lib/node.reducer.ts (1)
nodeCollectorReducer(107-326)packages/davinci-client/src/lib/davinci.types.ts (2)
Fido2RegistrationOptions(163-171)Fido2AuthenticationOptions(183-191)
packages/davinci-client/src/lib/client.store.ts (2)
packages/davinci-client/src/lib/client.store.utils.ts (1)
handleUpdateValidateError(51-66)packages/davinci-client/src/lib/collector.types.ts (7)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-307)Fido2AuthenticationInputValue(309-311)SingleValueCollectors(174-179)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
packages/davinci-client/src/lib/collector.utils.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.types.ts (7)
SingleValueAutoCollectorTypes(548-548)ObjectValueAutoCollectorTypes(549-552)InferAutoCollectorType(618-630)ValidatedTextCollector(184-184)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Mend Code Security Check
- GitHub Check: pr
🔇 Additional comments (27)
packages/davinci-client/src/lib/collector.types.test-d.ts (1)
305-305: LGTM! Test reflects nullable validation field.The addition of
validation: nullcorrectly tests the expanded input shape for multi-value collectors, aligning with the broader changes to make validation fields optional across the collector type system.packages/davinci-client/src/lib/node.reducer.test.ts (2)
440-440: LGTM! Validation field updates are consistent.The addition of
validation: nullacross these test expectations correctly reflects the expanded input shapes that now include optional validation metadata. This change is consistent with the broader type system updates for multi-value and object-value collectors.Also applies to: 475-475, 526-526, 576-576, 634-634, 677-677, 742-742, 786-786, 826-826, 852-852
867-923: LGTM! Comprehensive ProtectCollector test coverage.The test suite properly validates the ProtectCollector's update pathway, including the correct input structure, configuration mapping, and value updates. The test expectations align with the SingleValueAutoCollector category and the Protect-specific configuration schema.
packages/davinci-client/src/lib/davinci.types.ts (4)
152-153: LGTM! Phone number validation flag added.The addition of the
validatePhoneNumber: booleanfield extends the PhoneNumberField type to support validation control, which aligns with the validation enhancements across the collector system.
163-191: LGTM! FIDO2 option interfaces are properly exported.The
Fido2RegistrationOptionsandFido2AuthenticationOptionsinterfaces are correctly exported and properly extend the WebAuthn spec types. The overrides forchallenge,user, andallowCredentialscorrectly usenumber[]arrays instead ofBufferSourcetypes, which aligns with the DaVinci API's JSON-serializable format.
173-201: LGTM! FIDO2 field types are well-structured.The
Fido2RegistrationFieldandFido2AuthenticationFieldtypes properly capture the FIDO2 flow metadata, including the credential options, action discriminators, trigger mechanisms, and required flags. The discriminated union on theactionfield ('REGISTER' vs 'AUTHENTICATE') enables type-safe handling in downstream code.
212-218: LGTM! SingleValueFields union expanded correctly.The union now includes
ProtectField,Fido2RegistrationField, andFido2AuthenticationField, properly extending the single-value field types to support the new auto-collector pathways.packages/davinci-client/src/lib/collector.utils.test.ts (4)
480-480: LGTM! Validation field updates are consistent.The addition of
validation: nullacross these test expectations correctly reflects the nullable validation field introduced in the type definitions. This ensures tests remain aligned with the updated collector interfaces.Also applies to: 631-631, 671-671, 713-713, 754-754
812-842: LGTM! ProtectCollector test is comprehensive.The test validates the
returnSingleValueAutoCollectorutility with a ProtectField, correctly verifying the category, type, input/output structures, and configuration mapping. The test expectations align with the SingleValueAutoCollector category and Protect-specific config schema.
844-959: LGTM! FIDO2 collector tests are thorough.Both Fido2RegistrationCollector and Fido2AuthenticationCollector tests comprehensively validate the
returnObjectValueAutoCollectorutility, including:
- Correct category assignment (ObjectValueAutoCollector)
- Proper input/output structure mapping
- Configuration extraction from field properties
- Validation array handling (required vs null)
- Action discriminator handling
The mock credential options are realistic and align with WebAuthn specifications.
997-997: LGTM! Empty multi-value corrected.Changing the empty value expectation from
{}to[]correctly reflects that multi-value collectors expect array values, not object values. This aligns with the MultiValueCollector input type definition wherevalueisstring[].packages/davinci-client/src/lib/collector.types.ts (8)
205-205: LGTM! Validation field made nullable.Making the
validationfield nullable (ValidationRequired[] | null) allows collectors to explicitly represent the absence of validation rules, which is appropriate for optional validation scenarios. This change is consistently applied across multi-value collector interfaces.Also applies to: 226-226
305-311: LGTM! FIDO2 input value interfaces added.The
Fido2RegistrationInputValueandFido2AuthenticationInputValueinterfaces properly capture the WebAuthn credential payloads. Using optional properties forattestationValueandassertionValueallows these collectors to start with empty input and be populated after credential ceremonies complete.
326-326: LGTM! Object collector validation fields updated.Consistently making the
validationfield nullable across object-value collector interfaces allows explicit representation of no-validation scenarios. The expansion to includeValidationPhoneNumberin line 375 properly supports phone number validation rules.Also applies to: 350-350, 375-375
547-553: LGTM! AutoCollector taxonomy expanded.The split into
SingleValueAutoCollectorTypesandObjectValueAutoCollectorTypeswith a unifiedAutoCollectorTypesunion properly organizes the new FIDO2 collectors alongside the existing Protect collector. The addition ofObjectValueAutoCollectortoAutoCollectorCategoriesenables category-based discrimination in the type system.
558-558: LGTM! Generic parameter renamed for clarity.Renaming the generic from
VtoIV(Input Value) more clearly indicates this type parameter represents the input value shape rather than a generic value. This improves code readability and self-documentation.Also applies to: 567-567
578-602: LGTM! New auto-collector types properly defined.The new collector types (
ProtectCollector,Fido2RegistrationCollector,Fido2AuthenticationCollector,ObjectValueAutoCollector) are correctly defined using theAutoCollectorgeneric with appropriate categories, type literals, and input value types. The type parameters properly constrain the input values to their respective shapes.
604-609: LGTM! AutoCollectors union expanded correctly.The
AutoCollectorsunion now includes all five auto-collector types, enabling exhaustive pattern matching and type narrowing across the FIDO2 and Protect flows.
618-630: LGTM! Type inference expanded for new collectors.The
InferAutoCollectorTypeconditional type properly maps each collector type literal to its corresponding type, with a sensible fallback toSingleValueAutoCollectorfor unmapped cases. The inference chain correctly handles all five auto-collector variants.packages/davinci-client/src/lib/client.store.ts (3)
37-38: LGTM! Necessary type imports added.The FIDO2 input value types are correctly imported to support the new collector types in the update method signature.
266-279: Verify that SingleValueAutoCollector category is intentionally excluded from validation.The update method now accepts both
SingleValueAutoCollectorandObjectValueAutoCollectorcategories. However, in the validate method (lines 338-349), onlyObjectValueAutoCollectoris allowed whileSingleValueAutoCollectoris excluded. This appears intentional since ProtectCollector (a SingleValueAutoCollector) may not have validation rules. Please confirm this design decision is correct.
281-288: LGTM! Function signature correctly expanded to handle FIDO2 input values.The updater function signature now properly includes
Fido2RegistrationInputValueandFido2AuthenticationInputValueto support the new ObjectValueAutoCollector types.packages/davinci-client/src/lib/collector.utils.ts (5)
267-324: LGTM! Well-refactored single-value auto collector.The refactored
returnSingleValueAutoCollectorappropriately narrows the scope toProtectFieldand initializes the input value to an empty string. The removal of thedataparameter makes sense since auto collectors don't receive prefilled data.
326-401: LGTM! FIDO2 object-value auto collector implementation is solid.The new
returnObjectValueAutoCollectorfunction properly handles FIDO2 registration and authentication collectors with:
- Appropriate object-value initialization (
{})- Conditional validation when
requiredis true- Proper branching on
field.actionto distinguish registration from authentication- Consistent use of
nullfor empty validation arraysThe implementation aligns well with the existing collector patterns.
507-507: Excellent! Validation consistency improved.The validation assignment has been standardized to use
nullinstead ofundefinedwhen the validation array is empty (lines 507, 634). This resolves the inconsistency that was flagged in previous reviews and aligns with the pattern used in the new FIDO2 collectors (lines 365, 388).Also applies to: 634-634
571-587: LGTM! Defensive programming with optional chaining.The addition of optional chaining (
field.options?.map) with nullish coalescing (?? []) provides better safety against undefined options while maintaining the expected array return type. This prevents potential runtime errors.Also applies to: 599-606
718-725: LGTM! Validator signature correctly expanded for object values.The
returnValidatorfunction signature now acceptsAutoCollectorsand handlesRecord<string, unknown>values, which is necessary for validating FIDO2 collectors with object-shaped input values. The function logic appropriately handles empty objects in the required validation check.
ancheetah
force-pushed
the
SDKS-4372-webauthn-collectors
branch
from
7471c5c to
c1ae746
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
packages/davinci-client/src/lib/davinci.types.ts (1)
183-191: Authentication options fix is correct; minor optional tweak
allowCredentialsnaming and array shape are correct.- Optional: consider
readonly number[]forchallenge/idto signal immutability (non-blocking).Also applies to: 193-201
packages/davinci-client/src/lib/client.store.ts (2)
281-289: Type-safety improvement: specialize updater value by collector typeCurrent
valueunion permits shapes that don’t apply to some collectors. Consider a generic signature to infer the expected value from the collector, reducing runtime errors.Example approach (illustrative):
- Define
UpdaterFor<C>mapping collector → expected value.- Change
update<C extends AllowedCollectors>(collector: C): (value: UpdaterFor<C>, index?: number) => ...Would you like a typed diff introducing
UpdaterForand updatingupdateaccordingly?
310-315: Validate signature vs runtime gating
validateacceptsAutoCollectors, but onlyObjectValueAutoCollectoris validated at runtime. Either:
- Narrow the parameter type to only validatable categories, or
- Add a brief JSDoc clarifying that only some categories have validation rules.
Non-blocking; current behavior is safe due to gating.
Also applies to: 338-346
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (13)
.changeset/tired-melons-wish.md(1 hunks)packages/davinci-client/src/lib/client.store.ts(4 hunks)packages/davinci-client/src/lib/collector.types.test-d.ts(1 hunks)packages/davinci-client/src/lib/collector.types.ts(10 hunks)packages/davinci-client/src/lib/collector.utils.test.ts(8 hunks)packages/davinci-client/src/lib/collector.utils.ts(10 hunks)packages/davinci-client/src/lib/davinci.types.ts(3 hunks)packages/davinci-client/src/lib/davinci.utils.ts(2 hunks)packages/davinci-client/src/lib/node.reducer.test.ts(12 hunks)packages/davinci-client/src/lib/node.reducer.ts(8 hunks)packages/davinci-client/src/lib/node.types.test-d.ts(2 hunks)packages/davinci-client/src/lib/node.types.ts(2 hunks)packages/journey-client/package.json(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- packages/davinci-client/src/lib/davinci.utils.ts
- packages/davinci-client/src/lib/collector.types.ts
🧰 Additional context used
🧬 Code graph analysis (7)
packages/davinci-client/src/lib/node.types.test-d.ts (1)
packages/davinci-client/src/lib/collector.types.ts (2)
Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)
packages/davinci-client/src/lib/node.types.ts (1)
packages/davinci-client/src/lib/collector.types.ts (2)
Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)
packages/davinci-client/src/lib/client.store.ts (2)
packages/davinci-client/src/lib/client.store.utils.ts (1)
handleUpdateValidateError(51-66)packages/davinci-client/src/lib/collector.types.ts (7)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-307)Fido2AuthenticationInputValue(309-311)SingleValueCollectors(174-179)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
packages/davinci-client/src/lib/node.reducer.ts (2)
packages/davinci-client/src/lib/collector.types.ts (5)
PhoneNumberInputValue(295-298)Fido2RegistrationInputValue(305-307)Fido2AuthenticationInputValue(309-311)Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)packages/davinci-client/src/lib/collector.utils.ts (3)
returnProtectCollector(439-441)returnFido2RegistrationCollector(449-451)returnFido2AuthenticationCollector(459-461)
packages/davinci-client/src/lib/collector.utils.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.types.ts (7)
SingleValueAutoCollectorTypes(548-548)ObjectValueAutoCollectorTypes(549-552)InferAutoCollectorType(618-630)ValidatedTextCollector(184-184)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
packages/davinci-client/src/lib/collector.utils.test.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)Fido2RegistrationField(173-181)Fido2AuthenticationField(193-201)packages/davinci-client/src/lib/collector.utils.ts (2)
returnSingleValueAutoCollector(273-324)returnObjectValueAutoCollector(333-401)
packages/davinci-client/src/lib/node.reducer.test.ts (4)
packages/davinci-client/src/lib/collector.types.ts (3)
ProtectCollector(578-582)Fido2RegistrationCollector(583-587)Fido2AuthenticationCollector(588-592)packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)packages/davinci-client/src/lib/node.reducer.ts (1)
nodeCollectorReducer(107-326)packages/davinci-client/src/lib/davinci.types.ts (2)
Fido2RegistrationOptions(163-171)Fido2AuthenticationOptions(183-191)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Mend Code Security Check
- GitHub Check: Mend Security Check
🔇 Additional comments (30)
packages/journey-client/package.json (1)
36-36: Align vite versions in dependencies and devDependencies, and clarify if this change is intentional.The version mismatch is confirmed: vite 6.3.6 in dependencies (line 36) and vite 6.3.4 in devDependencies (line 41). This divergence should be resolved by updating devDependencies to match:
"devDependencies": { "@vitest/coverage-v8": "^1.2.0", - "vite": "6.3.4", + "vite": "6.3.6", "vitest": "^1.2.0" }Please confirm whether this vite version bump to 6.3.6 is necessary for the FIDO2 collector changes or if it is incidental.
.changeset/tired-melons-wish.md (1)
1-5: Changeset looks goodMinor bump and succinct summary for adding WebAuthn/FIDO2 collectors is appropriate.
packages/davinci-client/src/lib/collector.types.test-d.ts (1)
301-307: Type test aligns with new nullable validationAdding
validation: nullmatches updated collector input shape (ValidationRequired[] | null).packages/davinci-client/src/lib/davinci.types.ts (3)
152-154: PhoneNumberField additions OK
requiredandvalidatePhoneNumberfields look correct and consistent with other fields.
163-171: FIDO2 registration types are well-formedExported
Fido2RegistrationOptionsandFido2RegistrationFieldmirror WebAuthn, with binary IDs represented asnumber[]. Looks good.Also applies to: 173-181
212-218: Union extension is appropriateIncluding FIDO2 fields in
SingleValueFieldsaligns with how fields are grouped for rendering.packages/davinci-client/src/lib/client.store.ts (1)
271-276: Category gating for update is correctAllowing both SingleValueAutoCollector and ObjectValueAutoCollector is needed for Protect and FIDO2 paths.
packages/davinci-client/src/lib/node.types.test-d.ts (1)
36-38: Collector union tests updated correctlyIncluding FIDO2 collectors in the
Collectorsunion checks matches the new public surface.Also applies to: 221-241
packages/davinci-client/src/lib/node.types.ts (1)
26-27: LGTM! Clean type extension for FIDO2 support.The addition of
Fido2RegistrationCollectorandFido2AuthenticationCollectorto the public type exports andCollectorsunion is consistent with the broader FIDO2 support being added across the codebase.Also applies to: 47-48
packages/davinci-client/src/lib/node.reducer.test.ts (4)
440-440: LGTM! Consistent validation handling.Adding
validation: nullto the input shapes across multiple collectors standardizes the validation property handling throughout the test suite, aligning with the updated collector factory functions.Also applies to: 475-475, 526-526, 576-576, 634-634, 677-677, 742-742, 786-786, 826-826, 852-852
867-923: LGTM! Comprehensive ProtectCollector test coverage.The test properly validates the update flow for ProtectCollector with SingleValueAutoCollector category, ensuring correct value assignment.
925-1028: LGTM! Thorough Fido2RegistrationCollector test coverage.The test validates the complete update flow for FIDO2 registration, including the ObjectValueAutoCollector category, input value structure with attestation, and output configuration with publicKeyCredentialCreationOptions.
1030-1117: LGTM! Comprehensive Fido2AuthenticationCollector test coverage.The test properly validates the update flow for FIDO2 authentication, covering the ObjectValueAutoCollector category, input value structure with assertion, and output configuration with publicKeyCredentialRequestOptions.
packages/davinci-client/src/lib/node.reducer.ts (6)
29-30: LGTM! Necessary imports for FIDO2 support.The new imports for
returnFido2RegistrationCollector,returnFido2AuthenticationCollector, and their associated types align with the broader FIDO2 functionality being added.Also applies to: 52-55
70-75: LGTM! Proper type extension for FIDO2 input values.Extending the
updateCollectorValuesaction's value union to includeFido2RegistrationInputValueandFido2AuthenticationInputValuecorrectly handles the object-based input structures required for WebAuthn flows.
99-100: LGTM! Consistent initial state extension.Adding the new FIDO2 collector types to
initialCollectorValuesmaintains consistency with the extended collector system.
179-189: LGTM! Clean FIDO2 routing logic.The updated
returnProtectCollectorcall (removing the data parameter) aligns with the refactored function signature. The new FIDO2 branch properly routes to registration or authentication collectors based on thefield.actiondiscriminator. Thebreakstatement ensures that iffield.actionis neither 'REGISTER' nor 'AUTHENTICATE', execution falls through to the generic collector handling below, which is appropriate fallback behavior.
225-235: LGTM! Correct type narrowing for ProtectCollector.The condition now checks
collector.type === 'ProtectCollector'instead of category, which correctly handles the ProtectCollector as a SingleValueAutoCollector with string input values. This aligns with the new collector categorization where ProtectCollector has the category 'SingleValueAutoCollector' but needs special handling.
300-324: LGTM! Proper FIDO2 input validation and assignment.Both
Fido2RegistrationCollectorandFido2AuthenticationCollectorupdate handlers correctly:
- Validate that
idis a string (required for tracking)- Validate that
valueis an object- Check for required properties (
attestationValueorassertionValue)- Assign the value to
collector.input.valueThis follows the same pattern as the existing
PhoneNumberCollectorhandler and provides appropriate error messages.packages/davinci-client/src/lib/collector.utils.test.ts (4)
23-24: LGTM! Updated imports for new auto-collector API.The new imports
returnSingleValueAutoCollectorandreturnObjectValueAutoCollectoralong with the FIDO2 and Protect field types enable testing of the refactored auto-collector functionality.Also applies to: 30-33
480-480: LGTM! Consistent validation handling across tests.Setting
validation: nullfor collectors without validation rules and updating the multi-value validator test expectation from{}to[]standardizes the validation property handling throughout the test suite.Also applies to: 526-526, 576-576, 631-631, 671-671, 713-713, 754-754, 997-997
812-842: LGTM! Comprehensive ProtectCollector test.The test validates the
returnSingleValueAutoCollectorfunction with aProtectField, verifying the correct SingleValueAutoCollector category, input/output structure, and config mapping for behavioral data collection and device identification settings.
844-959: LGTM! Thorough FIDO2 collector tests.Both test cases comprehensively validate:
Fido2RegistrationCollector: ObjectValueAutoCollector category, empty object input value initialization, required validation whenrequired: true, and config with publicKeyCredentialCreationOptionsFido2AuthenticationCollector: Similar structure withrequired: falseresulting invalidation: null, and config with publicKeyCredentialRequestOptionsThe tests properly cover the two FIDO2 action types and their distinct option structures.
packages/davinci-client/src/lib/collector.utils.ts (7)
29-31: LGTM! Necessary type imports for auto-collector refactoring.The imports for
AutoCollectors,SingleValueAutoCollectorTypes,ObjectValueAutoCollectorTypes, and the FIDO2 field types support the new auto-collector API structure.Also applies to: 36-37
267-324: LGTM! Refactored for single-value auto-collectors.The renamed
returnSingleValueAutoCollectorfunction correctly:
- Narrows the field type to
ProtectField- Removes the
dataparameter and always initializesvalueto an empty string (appropriate for auto-collected fields that are populated automatically)- Uses
SingleValueAutoCollectorTypesfor type narrowing- Returns proper structure for ProtectCollector with config object
This aligns with the past review discussion about removing prefilled data handling for auto-collectors.
326-401: LGTM! New object-value auto-collector for FIDO2.The
returnObjectValueAutoCollectorfunction properly:
- Handles
Fido2RegistrationField | Fido2AuthenticationFieldwithObjectValueAutoCollectorTypes- Initializes input value to an empty object
{}- Adds required validation when
field.required === true- Uses
validation: nullwhen the validation array is empty (consistent with the broader standardization)- Branches on
field.action('REGISTER' vs 'AUTHENTICATE') to return the appropriate config with eitherpublicKeyCredentialCreationOptionsorpublicKeyCredentialRequestOptionsThe use of
nullfor empty validation is consistent with the pattern established in other collectors and aligns with the past review discussion.
439-461: LGTM! Clean factory functions for FIDO2 collectors.The updated
returnProtectCollectornow delegates toreturnSingleValueAutoCollectorwithout a data parameter, and the newreturnFido2RegistrationCollectorandreturnFido2AuthenticationCollectorfunctions provide convenient wrappers that delegate toreturnObjectValueAutoCollector. This follows the established pattern in the file.
507-507: LGTM! Standardized validation handling.Setting
validationtonullwhen the validation array is empty (rather thanundefined) provides consistency across all collectors. This aligns with the past review discussion about standardizing validation property handling.Also applies to: 634-634
571-587: LGTM! Added defensive optional chaining.The optional chaining operators (
field.options?.) prevent potential runtime errors if the options array is unexpectedly undefined, even though type constraints should ensure options exist. The nullish coalescing (?? []) provides a safe fallback to an empty array.Also applies to: 599-606
718-725: LGTM! Extended validator to support auto-collectors.The
returnValidatorfunction now acceptsAutoCollectorsin its union type and the return function acceptsRecord<string, unknown>as a possible value type. This properly handles validation for the new FIDO2 object-value collectors that work with complex objects rather than just strings or arrays.
|
|
||
| describe('The node collector reducer with Fido2RegistrationFieldValue', () => { | ||
| it('should handle collector updates ', () => { | ||
| // todo: declare inputValue type as Fido2RegistrationInputValue |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Address the TODO comments for type declarations.
The TODO comments indicate that the mockInputValue variables should be explicitly typed as Fido2RegistrationInputValue and Fido2AuthenticationInputValue respectively. This would improve type safety and make the test intentions clearer.
Apply this diff to add explicit type declarations:
- // todo: declare inputValue type as Fido2RegistrationInputValue
- const mockInputValue = {
+ const mockInputValue: Fido2RegistrationInputValue = {
attestationValue: {And for the authentication test:
- // todo: declare inputValue type as Fido2AuthenticationInputValue
- const mockInputValue = {
+ const mockInputValue: Fido2AuthenticationInputValue = {
assertionValue: {Also applies to: 1032-1032
🤖 Prompt for AI Agents
In packages/davinci-client/src/lib/node.reducer.test.ts around lines 927 and
1032, the test TODOs require explicit typing for the mock input values: change
the declaration at line 927 to declare mockInputValue as
Fido2RegistrationInputValue and the declaration at line 1032 to declare
mockInputValue as Fido2AuthenticationInputValue; ensure those types are imported
from their source (or available in scope) and adjust any object literal fields
to satisfy the type if the compiler surfaces errors.
c1ae746 to
a9cc3db
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Nx Cloud is proposing a fix for your failed CI:
We've restored the optional data parameter to the returnProtectCollector function and updated the node reducer to pass prefilled data when available. This ensures Protect collectors can be initialized with existing data from formData, maintaining compatibility with the existing Protect SDK integration.
We verified this fix by re-running @forgerock/davinci-suites:e2e-ci--src/protect.test.ts.
Suggested Fix changes
diff --git a/packages/davinci-client/src/lib/collector.utils.ts b/packages/davinci-client/src/lib/collector.utils.ts
index 6865b44..533f919 100644
--- a/packages/davinci-client/src/lib/collector.utils.ts
+++ b/packages/davinci-client/src/lib/collector.utils.ts
@@ -434,10 +434,15 @@ export function returnSingleSelectCollector(field: SingleSelectField, idx: numbe
* @function returnProtectCollector - Creates a ProtectCollector object based on the provided field and index.
* @param {DaVinciField} field - The field object containing key, label, type, and links.
* @param {number} idx - The index to be used in the id of the ProtectCollector.
+ * @param {string} [data] - Optional data to prefill the collector with.
* @returns {ProtectCollector} The constructed ProtectCollector object.
*/
-export function returnProtectCollector(field: ProtectField, idx: number) {
- return returnSingleValueAutoCollector(field, idx, 'ProtectCollector');
+export function returnProtectCollector(field: ProtectField, idx: number, data?: string) {
+ const collector = returnSingleValueAutoCollector(field, idx, 'ProtectCollector');
+ if (data) {
+ collector.input.value = data;
+ }
+ return collector;
}
/**
diff --git a/packages/davinci-client/src/lib/node.reducer.ts b/packages/davinci-client/src/lib/node.reducer.ts
index 34ed242..36a8909 100644
--- a/packages/davinci-client/src/lib/node.reducer.ts
+++ b/packages/davinci-client/src/lib/node.reducer.ts
@@ -177,7 +177,8 @@ export const nodeCollectorReducer = createReducer(initialCollectorValues, (build
return returnSubmitCollector(field, idx);
}
case 'PROTECT': {
- return returnProtectCollector(field, idx);
+ const str = data as string;
+ return returnProtectCollector(field, idx, str);
}
case 'FIDO2': {
if (field.action === 'REGISTER') {
Or Apply changes locally with:
npx nx-cloud apply-locally 6YAS-Jj8r
Apply fix locally with your editor ↗ View interactive diff ↗
🎓 To learn more about Self Healing CI, please visit nx.dev
ancheetah
force-pushed
the
SDKS-4372-webauthn-collectors
branch
from
a9cc3db to
1a29b13
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
packages/davinci-client/src/lib/collector.utils.ts (2)
326-401: Validation assignment pattern is inconsistent with existing collectors.Lines 365 and 388 assign
nullwhenvalidationArrayis empty, which differs from the original pattern in this file where other collectors useundefined(e.g., lines 525, 652 in the original code). This inconsistency was already noted in previous review discussions.
507-507: Validation assignment changed fromundefinedtonull.This line previously used
undefinedwhenvalidationArraywas empty. The change tonullaligns with the new ObjectValueAutoCollector pattern but creates inconsistency with this function's previous behavior. This validation assignment inconsistency is already under discussion in previous review comments.
🧹 Nitpick comments (3)
packages/davinci-client/src/lib/node.reducer.test.ts (2)
925-1028: Good FidoRegistrationCollector test coverage.The test suite properly validates the FIDO2 registration flow with appropriate mock data. The test structure follows existing patterns and correctly validates the ObjectValueAutoCollector category and credential creation options.
Consider adding explicit type annotations to the mockInputValue for improved type safety and IDE support:
- // todo: declare inputValue type as Fido2RegistrationInputValue - const mockInputValue = { + const mockInputValue: FidoRegistrationInputValue = { attestationValue: {Note: This addresses the TODO comment and improves type checking.
1030-1117: Thorough FidoAuthenticationCollector test coverage.The test suite appropriately validates the FIDO2 authentication flow with proper mock assertion data and correctly validates the ObjectValueAutoCollector category and credential request options.
Consider adding explicit type annotation to the mockInputValue for improved type safety:
- // todo: declare inputValue type as Fido2AuthenticationInputValue - const mockInputValue = { + const mockInputValue: FidoAuthenticationInputValue = { assertionValue: {Note: This addresses the TODO comment and improves type checking.
packages/davinci-client/src/lib/client.store.ts (1)
281-288: Consider extracting the value parameter union into a named type.The value parameter union now includes five distinct types. While functional, extracting this into a named type (e.g.,
CollectorInputValue) would improve readability and maintainability, especially if more input value types are added in the future.Example:
type CollectorInputValue = | string | string[] | PhoneNumberInputValue | FidoRegistrationInputValue | FidoAuthenticationInputValue;Then use:
- return function ( - value: - | string - | string[] - | PhoneNumberInputValue - | FidoRegistrationInputValue - | FidoAuthenticationInputValue, - index?: number, - ) { + return function (value: CollectorInputValue, index?: number) {
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (13)
.changeset/tired-melons-wish.md(1 hunks)packages/davinci-client/src/lib/client.store.ts(4 hunks)packages/davinci-client/src/lib/collector.types.test-d.ts(1 hunks)packages/davinci-client/src/lib/collector.types.ts(10 hunks)packages/davinci-client/src/lib/collector.utils.test.ts(8 hunks)packages/davinci-client/src/lib/collector.utils.ts(10 hunks)packages/davinci-client/src/lib/davinci.types.ts(3 hunks)packages/davinci-client/src/lib/davinci.utils.ts(2 hunks)packages/davinci-client/src/lib/node.reducer.test.ts(12 hunks)packages/davinci-client/src/lib/node.reducer.ts(8 hunks)packages/davinci-client/src/lib/node.types.test-d.ts(2 hunks)packages/davinci-client/src/lib/node.types.ts(2 hunks)packages/journey-client/package.json(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- packages/davinci-client/src/lib/node.types.test-d.ts
- packages/davinci-client/src/lib/node.types.ts
🧰 Additional context used
🧬 Code graph analysis (7)
packages/davinci-client/src/lib/davinci.utils.ts (1)
packages/davinci-client/src/lib/collector.types.ts (3)
PhoneNumberInputValue(295-298)FidoRegistrationInputValue(305-307)FidoAuthenticationInputValue(309-311)
packages/davinci-client/src/lib/client.store.ts (2)
packages/davinci-client/src/lib/client.store.utils.ts (1)
handleUpdateValidateError(51-66)packages/davinci-client/src/lib/collector.types.ts (7)
PhoneNumberInputValue(295-298)FidoRegistrationInputValue(305-307)FidoAuthenticationInputValue(309-311)SingleValueCollectors(174-179)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
packages/davinci-client/src/lib/node.reducer.ts (2)
packages/davinci-client/src/lib/collector.types.ts (5)
PhoneNumberInputValue(295-298)FidoRegistrationInputValue(305-307)FidoAuthenticationInputValue(309-311)FidoRegistrationCollector(583-587)FidoAuthenticationCollector(588-592)packages/davinci-client/src/lib/collector.utils.ts (3)
returnProtectCollector(439-441)returnFidoRegistrationCollector(449-451)returnFidoAuthenticationCollector(459-461)
packages/davinci-client/src/lib/collector.types.ts (1)
packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)
packages/davinci-client/src/lib/collector.utils.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)FidoRegistrationField(173-181)FidoAuthenticationField(193-201)packages/davinci-client/src/lib/collector.types.ts (7)
SingleValueAutoCollectorTypes(548-548)ObjectValueAutoCollectorTypes(549-552)InferAutoCollectorType(618-630)ValidatedTextCollector(184-184)ObjectValueCollectors(396-401)MultiValueCollectors(250-252)AutoCollectors(604-609)
packages/davinci-client/src/lib/collector.utils.test.ts (2)
packages/davinci-client/src/lib/davinci.types.ts (3)
ProtectField(156-161)FidoRegistrationField(173-181)FidoAuthenticationField(193-201)packages/davinci-client/src/lib/collector.utils.ts (2)
returnSingleValueAutoCollector(273-324)returnObjectValueAutoCollector(333-401)
packages/davinci-client/src/lib/node.reducer.test.ts (4)
packages/davinci-client/src/lib/collector.types.ts (3)
ProtectCollector(578-582)FidoRegistrationCollector(583-587)FidoAuthenticationCollector(588-592)packages/davinci-client/src/types.ts (1)
ProtectCollector(51-51)packages/davinci-client/src/lib/node.reducer.ts (1)
nodeCollectorReducer(107-326)packages/davinci-client/src/lib/davinci.types.ts (2)
FidoRegistrationOptions(163-171)FidoAuthenticationOptions(183-191)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Mend Code Security Check
- GitHub Check: pr
🔇 Additional comments (24)
packages/journey-client/package.json (1)
36-36: Vite version mismatch confirmed: dependencies (6.3.6) vs devDependencies (6.3.4).The version inconsistency is verified. Line 36 sets vite to 6.3.6 in dependencies, while line 41 keeps it at 6.3.4 in devDependencies. This divergence between build and development environments should be resolved.
Align both to the same version:
"dependencies": { "@forgerock/sdk-logger": "workspace:*", "@forgerock/sdk-request-middleware": "workspace:*", "@forgerock/sdk-types": "workspace:*", "@forgerock/sdk-utilities": "workspace:*", "@forgerock/storage": "workspace:*", "@reduxjs/toolkit": "catalog:", "tslib": "^2.3.0", - "vite": "6.3.6", + "vite": "6.3.4", "vitest-canvas-mock": "^0.3.3" },Or update devDependencies to 6.3.6 to match dependencies. Confirm your intent—is this split deliberate or unintentional?
packages/davinci-client/src/lib/collector.types.test-d.ts (1)
305-305: LGTM! Type test correctly reflects nullable validation.The addition of
validation: nullin the type test correctly validates that theMultiSelectCollectortype allows null validation, consistent with the updated type definitions incollector.types.ts.packages/davinci-client/src/lib/davinci.types.ts (2)
163-201: Well-structured FIDO2 type definitions.The new
FidoRegistrationOptions,FidoAuthenticationOptions,FidoRegistrationField, andFidoAuthenticationFieldtypes are well-designed and align with the WebAuthn specification. The interfaces correctly extend the standard PublicKey credential types with appropriate customizations for the DaVinci client.
212-218: Good expansion of SingleValueFields union.The inclusion of
FidoRegistrationFieldandFidoAuthenticationFieldin theSingleValueFieldsunion correctly integrates the new FIDO2 field types into the existing type hierarchy.packages/davinci-client/src/lib/collector.types.ts (2)
305-311: Clean FIDO2 input value interfaces.The
FidoRegistrationInputValueandFidoAuthenticationInputValueinterfaces are appropriately simple and correctly use optional properties for the WebAuthn credential values.
547-630: Comprehensive AutoCollector type system expansion.The expansion of the AutoCollector type system to support object-value collectors is well-designed:
- Clear separation between
SingleValueAutoCollectorTypesandObjectValueAutoCollectorTypes- Proper generic parameter naming (
IVfor input value)- Complete type inference mapping
- Consistent union definitions
.changeset/tired-melons-wish.md (1)
1-5: Appropriate changeset for feature addition.The changeset correctly indicates a minor version bump for the new WebAuthn/FIDO2 collectors feature.
packages/davinci-client/src/lib/davinci.utils.ts (2)
25-30: Proper import of new FIDO2 input value types.The import statement correctly includes the new
FidoAuthenticationInputValueandFidoRegistrationInputValuetypes needed for the formData type union.
57-59: FormData union appropriately expanded.The formData type union now includes
FidoRegistrationInputValueandFidoAuthenticationInputValue, ensuring type safety when handling FIDO2 collector data in submit requests.packages/davinci-client/src/lib/node.reducer.test.ts (1)
867-923: Comprehensive ProtectCollector test coverage.The new test suite for
ProtectCollectorproperly validates the update flow, including the correct handling of theSingleValueAutoCollectorcategory and the config output structure.packages/davinci-client/src/lib/collector.utils.test.ts (3)
812-842: Solid test coverage for ProtectCollector utility.The test properly validates that
returnSingleValueAutoCollectorcreates a correctProtectCollectorwith the appropriate category, config output, and empty input value.
844-912: Comprehensive FidoRegistrationCollector test.The test thoroughly validates the
returnObjectValueAutoCollectorfunction for FIDO2 registration, including:
- Correct ObjectValueAutoCollector category
- Proper handling of required validation
- Complete publicKeyCredentialCreationOptions in config
- Empty object as initial input value
914-959: Well-structured FidoAuthenticationCollector test.The test appropriately validates FIDO2 authentication collector creation with:
- Correct ObjectValueAutoCollector category
- Null validation when not required
- Complete publicKeyCredentialRequestOptions in config
- Proper action and trigger values
packages/davinci-client/src/lib/node.reducer.ts (3)
179-189: Clean FIDO2 collector routing logic.The new FIDO2 case correctly routes to registration or authentication collectors based on the
field.actionproperty. The use of the action property for routing (as discussed in past reviews) is more concise and self-documenting than checking for property presence.
300-324: Robust FIDO2 collector update handlers.The update handlers for
FidoRegistrationCollectorandFidoAuthenticationCollectorfollow the established pattern with:
- Proper type guards and validation
- Clear, specific error messages
- Correct property validation (attestationValue for registration, assertionValue for authentication)
- Direct assignment of validated input values
228-228: Correct type check for ProtectCollector.The change from checking
SingleValueAutoCollectorcategory to checkingProtectCollectortype is appropriate, as it provides more specific type narrowing for the Protect-specific update logic.packages/davinci-client/src/lib/client.store.ts (3)
37-38: LGTM!The new FIDO2 input value type imports are necessary and correctly sourced.
309-314: LGTM!The validate method signature correctly extends to accept AutoCollectors, consistent with the update method changes.
338-349: LGTM!The validation category checks correctly include ObjectValueAutoCollector, and the error messaging is appropriately generic and consistent with the update method.
packages/davinci-client/src/lib/collector.utils.ts (5)
29-37: LGTM!The new imports for AutoCollector types and FIDO2 field types are necessary and correctly sourced.
267-324: LGTM!The function rename to
returnSingleValueAutoCollectorcorrectly reflects the narrowed type scope, and the removal of thedataparameter is appropriate for auto-collectors that don't support prefilled data.
439-441: LGTM!The refactored
returnProtectCollectorcorrectly delegates toreturnSingleValueAutoCollectorand the removal of thedataparameter is appropriate.
443-461: LGTM!The new FIDO2 collector wrapper functions follow the established pattern and correctly delegate to
returnObjectValueAutoCollectorwith appropriate type parameters.
571-606: LGTM!The addition of optional chaining for
field.optionsis a defensive improvement that prevents potential runtime errors. The nullish coalescing fallback to empty arrays is appropriate.
| * @param {ValidatedTextCollector | ObjectValueCollectors | MultiValueCollectors | AutoCollectors} collector - The collector to which the value will be validated | ||
| * @returns {function} - A "validator" function that validates the input value | ||
| */ | ||
| export function returnValidator( | ||
| collector: ValidatedTextCollector | ObjectValueCollectors | MultiValueCollectors, | ||
| collector: ValidatedTextCollector | ObjectValueCollectors | MultiValueCollectors | AutoCollectors, | ||
| ) { | ||
| const rules = collector.input.validation; | ||
| return (value: string | string[] | Record<string, string>) => { | ||
| return (value: string | string[] | Record<string, unknown>) => { |
There was a problem hiding this comment.
Return type incorrectly weakened to unknown.
Line 725 changes the return type to unknown, but the implementation still returns string[] (line 748). This unnecessarily weakens type safety and could cause issues for consumers expecting the more specific string[] type.
Apply this diff to restore proper typing:
- return (value: string | string[] | Record<string, unknown>) => {
+ return (value: string | string[] | Record<string, unknown>): string[] => {🤖 Prompt for AI Agents
In packages/davinci-client/src/lib/collector.utils.ts around lines 718 to 725,
the function return type was weakened to unknown even though the implementation
returns string[]; change the function's return type from unknown to the concrete
type (string[]) so the validator signature reflects the actual return value,
ensuring callers receive the proper typed result and restoring type safety.
|
Updated naming |
3 participants
JIRA Ticket
https://pingidentity.atlassian.net/browse/SDKS-4372
Description
Adds FIDO2 registration and authentication collectors and unit tests
TODO: changeset?
Summary by CodeRabbit
New Features
Bug Fixes
Tests