fix: show numOpportunities in agent table (#712)#772
Open
ivannissimrch wants to merge 5 commits into
Open
Conversation
Collaborator
|
@ivannissimrch Ivan pls merge the fresh |
# Conflicts: # package.json # yarn.lock
Collaborator
Author
|
@arturasmckwcz I just merged the latest develop. |
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.
Description
The Agents (Einrichtungen) table's opportunities column always showed "—" because the agent list response didn't include an opportunities count. be#738 added
numOpportunitiesto the/agentlist response (exposed in SDK 0.0.119), so the frontend can now display the real count.Related Issues
Closes #712
Changes
need4deed-sdkto0.0.119, which addsnumOpportunitiesandemailtoApiAgentGetListemailcast,emailis on the SDK type as of 0.0.119Note:
number of opportunities still displays "-" The column will populate with numbers once the dev backend is redeployed with be#738
Checklist