Chi 3295 formdef package move#2962
Merged
Merged
Conversation
…ependency so flex can import it
gpaoloni
changed the base branch from
master
to
CHI-3295-update_prepopulate_logic
…e_defs CHI-3295: use new prepopulate config in Twilio Lambda
# Conflicts: # lambdas/account-scoped/src/hrm/populateHrmContactFormFromTaskByKeys.ts # lambdas/packages/hrm-form-definitions/form-definitions/as/v1/PostSurvey.json # lambdas/packages/hrm-form-definitions/package.json
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Review after #2958 merged
Description
Moves
hrm-form-definitionsunderlambda/packagesso it can be used in the lambdas workspace.A few additional dependency and workflow updates were also required
Checklist
Other Related Issues
None
Verification steps
AFTER YOU MERGE
You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P