This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
feat: handle nonslug program keys from discovery #596
Merged
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.
Description
This Discovery ADR changed the way Program marketing slugs are generated such that they are no longer guaranteed to be a valid SlugField which makes them unsafe to use as url tokens. Because Registrar supports these values deviating from the source in discovery we're able to translate any non-slug values to something that will work with Registrar and any UI's that rely on it (Program Console + Learner Portal).
This change will only impact new programs moving forward since we do not modify a programs key after a record with that UUID has been synced. This is done to support custom external keys for partners that need a specific value and works to our benefit here.
2U-Internal Ticket: COSMO-185