Is "Grouped by teams" necessary when the data is displayed in a table which has a "Filter by teams" feature?
Not necessary, render all without grouping in table
Should the User Subs / Prefixed Subs and TxnID subs options be tabs, rather than a filter dropdown like other ways to organize the data?
should be tabs because the data rendered in the table is different, designs to come
what is the checkmark icon representing in the table? The only action available there is to delete the ACL.
it was an extra feature to allow users to approve pending ACLs from this screen, but will not be part of this epic
in the Angular app, there are options to view service account password and offset info, but not in the new design. Are we not implementing those features?
we will, but designs are to come
![Screenshot 2023-05-15 at 14 33 56](
![Screenshot 2023-05-15 at 14 33 59](
hashtaghashtaghashtag API
There is no param exposed by the getTopicOverview endpoint to filter by ACL Type, team, or any search. These could be implemented only in the front end but only if the aclInfoList, prefixedAclInfoList and transactionalAclInfoList are not paginated. Their data type is AclInfo[], and I do see pagination properties on AclInfo. However, I do not see pagination info in the payload returned from that endpoint in staging (even for an array with > 10 elements):
![Screenshot 2023-05-15 at 14 31 44](
that data is never paginated
There is no "Time of request" in the ACL info data, but it is shown in the designs
All properties are optional in the payload we get from getTopicOverview
AclInfo has ccl_ssl and acl_ssls / acl_ip and acl_ips. What is the difference? Should there be only one property for it?
hashtag What is currently missing?
![Screenshot 2023-05-15 at 11 54 07](
hashtag Questions
hashtaghashtaghashtag UI
hashtaghashtaghashtag API
getTopicOverview
endpoint to filter by ACL Type, team, or any search. These could be implemented only in the front end but only if theaclInfoList
,prefixedAclInfoList
andtransactionalAclInfoList
are not paginated. Their data type isAclInfo[]
, and I do see pagination properties onAclInfo
. However, I do not see pagination info in the payload returned from that endpoint in staging (even for an array with > 10 elements): ![Screenshot 2023-05-15 at 14 31 44](getTopicOverview
AclInfo
hasccl_ssl
andacl_ssls
/acl_ip
andacl_ips
. What is the difference? Should there be only one property for it?hashtag TODO