-
Notifications
You must be signed in to change notification settings - Fork 24
796: adds two new engagement types to NGO engagement #923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
DarrellRoberts
wants to merge
12
commits into
develop
Choose a base branch
from
darrell/feat/new-engagement-statuses
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
d698c8e
adds new agentengagement types
DarrellRoberts 9ed6d29
Merge branch 'develop' into darrell/feat/new-engagement-statuses
DarrellRoberts 037a500
adds new icons & color backgrounds
DarrellRoberts 0adae6c
corrects constant bug
DarrellRoberts 8c6d479
Merge branch 'develop' into darrell/feat/new-engagement-statuses
arturasmckwcz 26a494f
Merge branch 'develop' into darrell/feat/new-engagement-statuses
arturasmckwcz a126cd9
Merge branch 'develop' into darrell/feat/new-engagement-statuses
arturasmckwcz f36e1b5
resolves merge conflicts
DarrellRoberts d6025db
aligns statusMaps in dashboard/common
DarrellRoberts a890f18
Merge branch 'darrell/feat/new-engagement-statuses' of github.com:nee…
DarrellRoberts 59b970c
Merge branch 'develop' into darrell/feat/new-engagement-statuses
arturasmckwcz 7d5c296
Merge branch 'develop' into darrell/feat/new-engagement-statuses
need4deed File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correctness:
statusIconMapfurther down in this file was left unchanged forINCONTACT/TRIED_TO_CONTACT(stillSparkleIcon, same asNEW), even though this diff gives them distinct colors here, and the siblingDashboard/Profile/common/statusMaps.tsgives them distinct icons (ChatsCircleIcon/PhoneDisconnectIcon).Failure scenario: Any future caller of
Dashboard/common/StatusBadge.tsxfor engagement status will render the new colors paired with the wrong, stale icon, inconsistent with how the same statuses render on the agent profile page. Currently dormant becauseAgentCard.tsxonly feedsvolunteerSearch(notengagementStatus) into this specificStatusBadge, so it won't visibly break until that column is wired up — but the next person to consume this map has no reason to suspect the inconsistency.