This repository has been archived by the owner on Dec 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
Add simple progressive reg components and routes #811
Draft
B77Mills
wants to merge
23
commits into
parameter1:master
Choose a base branch
from
B77Mills:a-progressive-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
B77Mills
force-pushed
the
a-progressive-1
branch
from
December 13, 2023 18:08
dc21a83
to
9f711da
Compare
B77Mills
force-pushed
the
a-progressive-1
branch
from
February 15, 2024 19:53
22280c2
to
e5c76ee
Compare
Initial port from profile components and routes as it will have to support the same variation of inputs. It does have added logic to only display one question at the moment based on array of configured ids. example: [ givenName, familyName, phone, 618a8a62934f8400ad4beb8f] It will only display on unanswered question in order at the moment.
This will be used on the wrapping components to determing timing as to when it will next display. Guessing we will also have to add progression logic here… like number of ansered vs total.
Meaning postal code wont be asked unless country code is us, canada or mexico or other address related logic like region code is also not able to be asked based on country.
Everything is required when visible. Also update address field logic so that only the postalCode & regionCode fields are dependent on countryCode bein answered. Also add visible logic to consent input in oreder to display when not answered.
Add requiresPUI(progressive user input) and validation on the identityX access service call. this will allow us to add to the identityX access check on content landing pages in order to use progressive reg on content gate.
Initial port from profile components and routes as it will have to support the same variation of inputs. It does have added logic to only display one question at the moment based on array of configured ids. example: [ givenName, familyName, phone, 618a8a62934f8400ad4beb8f] It will only display on unanswered question in order at the moment.
B77Mills
force-pushed
the
a-progressive-1
branch
from
June 18, 2024 20:00
ae35371
to
721b29e
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial port from profile components and routes as it will have to support the same variation of inputs. It does have added logic to only display one question at the moment based on array of configured ids.
Example of what to add to the identityX config:
It will only display on unanswered question in order at the moment.