CHI-3069: HRM create lambda #2669
Merged
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
This was referenced Jan 13, 2025
Merged
GPaoloni
approved these changes
Jan 14, 2025
|
|
||
| export const eventTypes: EventType[] = [RESERVATION_ACCEPTED]; | ||
|
|
||
| // Temporarily copied to this repo, will share the flex types when we move them into the same repo |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Description
Related PRs
https://github.com/techmatters/infrastructure-config/pull/408
techmatters/hrm#800
techmatters/serverless#740
#2662 (this PR is a follow up for this one, review it first)
#2674 (follow on from this one, review after)
TODO:
Refactor repo to reuse contact and form definition types between Flex and Lambdas - for another PR
Tests (coming in a follow up)
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