Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Context & Action Info to show in what it is related to #377
In Stream Settings, on Exclude Tab; there are two text boxes for "Context" & "Action". Right now in the auto-complete results all the contexts & actions are being listed. But we can not make anything out of it just by looking at the Context Name / Action Name.
We can add additional details to display in the tool-tip maybe, just like we did in #338 & #352. Though I'm not sure which details to include in that.
@desaiuditd This is nice idea for better UX. The unique thing about Actions is that they are not Connector/Context specific. For instance, nearly every Connector and Context uses the "Updated" action, so listing all of those would actually be unhelpful.
I think the general idea was that people would see a record appear in the main Stream Records screen and decide "I don't need to track that" and then proceed to the Exclude tab to select the appropriate item(s) never to track again.
However, I do see your point on this. I'll have to think about this one a little longer.
@fjarrett What if connectors, contexts and actions were linked hierarchically? This could help with UX, and provide some additional flexibility. Currently actions and contexts exist side-by-side.
With this, you could set up the filter menus with headings (and sub headings). You would have 2 instances of
When the Users connector is chosen, the
Of course, this can still work with choosing multiple items from the lists.
There is a usage case that this change would detriment. For those people who don't want to see any
Plus, it provides access to a (imho) more common usage case of people who want to see
It's a big change. What do you think?
@lukecarbis I perfectly agree with you, there is definitely a need to exclude a combination of Connector/Context/Action rather excluding all instances of a single Action/Context.
/cc @fjarrett Please weigh on the importance of this one.
On review, I'm not sure the Connector > Context > Action hierarchy would work. However, we should be capitalising on the existing methodology by adding Heading to the lists. I don't think the UI would change much at all. There would be two small adjustments: