ui: DestinationInputDirect component #3588
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
Forfold
requested changes
Jan 10, 2024
tony-tvu
approved these changes
Jan 10, 2024
Forfold
approved these changes
Jan 11, 2024
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.
Description:
This PR introduces the DestinationInputDirect component which will be used as a generic component for non-search-selectable destinations (e.g., a phone number or email address)
Which issue(s) this PR fixes:
Part of #2639
Out of Scope:
DestinationFieldmeta-component will be in a separate PR.Screenshots:
Describe any introduced user-facing changes:
N/A
Describe any introduced API changes:
N/A
Additional Info:
Run
make storybookto interact with the new components.