Feature contact checks #230
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.
This pull request introduces backend configuration improvements and adds significant new functionality for managing "Contact Checks" in the frontend, including internationalization support for related UI strings in both English and Spanish. The most important changes are grouped below:
Backend and Environment Configuration:
FRONTEND_PUBLIC_URLenvironment variable tongen.base.env,ngen.dev.env.example, andngen.prod.env.exampleto support generating frontend links in emails and other integrations. [1] [2] [3]Frontend Functionality: Contact Check API Integration:
contactchecks.jsxwith API functions for CRUD operations, resending, confirming, and retrieving Contact Checks, including error handling and alert notifications.Internationalization:
translation.jsonfiles to support the new Contact Check features and improve UI feedback, including new button labels, status messages, and detailed field descriptions. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]