zregvart
commented
6 years ago Pushing this to backlog, we would need to change the model of connector/actions to include a grouping concept. Or perhaps this can be done vie tags? cc @syndesisio/uxd
Closed syndesis-bot closed 6 years ago
zregvart
commented
6 years ago Pushing this to backlog, we would need to change the model of connector/actions to include a grouping concept. Or perhaps this can be done vie tags? cc @syndesisio/uxd
zregvart
commented
6 years ago @syndesisio/uxd any chance on looking into this for this sprint, or we can push this to a later sprint?
dongniwang
commented
6 years ago @zregvart - I saw that #199 is closed. Is there a new epic or issue that this problem relates to? The action page already has a filter function. Just need to add a type (or categories) as a new column to the action list and allow users to filter on that.
cc: @amysueg @sjcox-rh
zregvart
commented
6 years ago @dongniwang we're using the #183 as the umbrella epic for all API connector issues, it's a bit easier on the board that way.
I think we only have tags that we can use and one action can have multiple tags, we copy those from Swagger specification for API connectors or specify manually when developing a connector. Would a column with Tags and the ability to filter on tags suffice here?
sjcox-rh
commented
6 years ago @zregvart Do you have an example of what some of the tags would be?
@dongniwang had explored action groupings a while back. Here is one design, not saying this is what we should do but if we want to move forward with this route, I can quickly put something together.
We could group actions via the tags you are mentioning. This design could be reused throughout other areas of ipaas as well where we need to group items. If we do group via tag, I think we should be able to filter via tags as well using the filter tool already implemented.
zregvart
commented
6 years ago The canonical example of tag use is on the reference petstore.swagger.io site. It shows that operations tagged with pet, store, and user are grouped together.
Mind you, nothing prohibits the use of multiple tags on a single operation, for instance if our own TODO app Swagger specification https://raw.githubusercontent.com/syndesisio/todo-example/master/swagger.yaml is loaded in editor.swagger.io same operations show up grouped under different tags. Not sure how widespread this is, or if it's just a quirk that we did when defining TODO app's Swagger specification.
amysueg
commented
6 years ago @zregvart The UX team discussed this item and we agreed it's a nice to have feature. However, given the full slate of UX designs required for TP4, we'd recommend moving this back to the backlog for future consideration after GA.
gashcrumb
commented
6 years ago Stale, re-open a proper epic when this can be dealt with.
chirino
commented
6 years ago This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a temporary error. The following address(es) deferred:
chirino@gmail.com Domain hiramchirino.com has exceeded the max emails per hour (168/150 (112%)) allowed. Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from o3.sgmail.github.com ([192.254.112.98]:14368)
by host313.hostmonster.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89_1)
(envelope-from bounces+848413-18a6-hiram=hiramchirino.com@sgmail.github.com)
id 1ewBa8-0023Y7-Dw
for hiram@hiramchirino.com; Wed, 14 Mar 2018 12:57:00 -0600
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=IonE7RCD+6l4R6OrO/WWEW2RArI=; b=QOi3LW9luLAMFWXS
z3VJIzI0PtTAkgKgXTJ43Czq/NHhbmJl0MdV6KzAYBN8RcDxMtRcCZgaEhekxKrq
YLtVfeQ3uZnogeUtN2m/0bWOv9MLnj3H5Z37xA7yBcuh8rxIenCCEDu4sa2xV6hN
hBTbK4xnR5UK4K3770ONFzdBE9w=
Received: by filter0051p1iad2.sendgrid.net with SMTP id filter0051p1iad2-23056-5AA97070-5
2018-03-14 18:56:48.137938676 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194])
by ismtpd0040p1mdw1.sendgrid.net (SG) with ESMTP id 4CcfO2_OTwGWC9WztcD07A
for hiram@hiramchirino.com; Wed, 14 Mar 2018 18:56:48.133 +0000 (UTC)
Date: Wed, 14 Mar 2018 18:56:48 +0000 (UTC)
From: Stan Lewis notifications@github.com
Reply-To: syndesisio/syndesis reply@reply.github.com
To: syndesisio/syndesis syndesis@noreply.github.com
Cc: Subscribed subscribed@noreply.github.com
Message-ID: syndesisio/syndesis/issues/118/373136993@github.com
In-Reply-To: syndesisio/syndesis/issues/118@github.com
References: syndesisio/syndesis/issues/118@github.com
Subject: Re: [syndesisio/syndesis] Grouping of connector actions (#118)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5aa9706fd6ab7_23bb2acafc474ec8324a6";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gashcrumb
X-GitHub-Recipient: chirino
X-GitHub-Reason: subscribed
List-ID: syndesisio/syndesis
----==_mimepart_5aa9706fd6ab7_23bb2acafc474ec8324a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Stale, re-open a proper epic when this can be dealt with.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/syndesisio/syndesis/issues/118#issuecomment-373136993 ----==_mimepart_5aa9706fd6ab7_23bb2acafc474ec8324a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Stale, re-open a proper epic when this can be dealt with.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
----==_mimepart_5aa9706fd6ab7_23bb2acafc474ec8324a6--
chirino
commented
6 years ago This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a temporary error. The following address(es) deferred:
chirino@gmail.com Domain hiramchirino.com has exceeded the max emails per hour (176/150 (117%)) allowed. Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from o8.sgmail.github.com ([167.89.101.199]:14548)
by host313.hostmonster.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89_1)
(envelope-from bounces+848413-18a6-hiram=hiramchirino.com@sgmail.github.com)
id 1ewBc4-0024O2-7o
for hiram@hiramchirino.com; Wed, 14 Mar 2018 12:59:00 -0600
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=heUHr7f2A7Ce8PWx8HPkHxHzQ5k=; b=ndsf8Ln7dkQXeWIp
E501qew9G83ISG1sQZ71q+5KU3TbL0CQClH1nqtxA46/wM+dp+KYk3h+wD/0BKH3
IXttHm1tb2rHSO16ZQ0ZKYfF9mEpVSS+0T1qGoCaGoNUoEFH/+UZjelK4oXj0Q13
xZGXh7+yW1ziV3ixKCQQbBwSO38=
Received: by filter0503p1las1.sendgrid.net with SMTP id filter0503p1las1-22763-5AA970E8-A
2018-03-14 18:58:48.415208099 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194])
by ismtpd0012p1iad2.sendgrid.net (SG) with ESMTP id peZig4ZBR4KgtkuHzwlEDQ
for hiram@hiramchirino.com; Wed, 14 Mar 2018 18:58:48.117 +0000 (UTC)
Date: Wed, 14 Mar 2018 18:58:48 +0000 (UTC)
From: Stan Lewis notifications@github.com
Reply-To: syndesisio/syndesis reply@reply.github.com
To: syndesisio/syndesis syndesis@noreply.github.com
Cc: Hiram Chirino hiram@hiramchirino.com,
Comment comment@noreply.github.com
Message-ID: syndesisio/syndesis/issue/118/issue_event/1521729070@github.com
In-Reply-To: syndesisio/syndesis/issues/118@github.com
References: syndesisio/syndesis/issues/118@github.com
Subject: Re: [syndesisio/syndesis] Grouping of connector actions (#118)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5aa970e8213cd_60942ac23ded8ecc2888a";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gashcrumb
X-GitHub-Recipient: chirino
X-GitHub-Reason: comment
List-ID: syndesisio/syndesis
----==_mimepart_5aa970e8213cd_60942ac23ded8ecc2888a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
Closed #118.
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/syndesisio/syndesis/issues/118#event-1521729070 ----==_mimepart_5aa970e8213cd_60942ac23ded8ecc2888a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
Closed #118.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
----==_mimepart_5aa970e8213cd_60942ac23ded8ecc2888a--
From https://github.com/syndesisio/syndesis/issues/199. Some connectors might have a long list of actions, we should provide a (common) way of grouping actions. Perhaps using
tags?