OLH-2416 Create client registry entries for each RP #4
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
saralk
changed the title
saralk
force-pushed
the
OLH-2416-move-all-client-registry-entries-over-to-the-new-l
branch
from
047295e to
dd52d49
Compare
|
is it worth looking at naming conventions for RPs and setting a standard as part of a separate ticket? |
latifcabinetoffice
approved these changes
Feb 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
What changed
Added a script to transfer RPs from the client registry in frontend over to this repo
The script uses the config the translation files to find the values required
It generates the config using a template
Also generates the
index.jsfile to export all the RP clientsRan the script and prettified all the RPs output.
Why did it change
Related links
Checklists
Testing
Sign-offs
How to review