Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Fri, 30 Jun 2017 02:50:00 +0000 (UTC)
From: "Ilya Borisov (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.13083656.1498790961000.141182.1498791000337@Atlassian.JIRA>
In-Reply-To: <JIRA.13083656.1498790961000@Atlassian.JIRA>
References: <JIRA.13083656.1498790961000@Atlassian.JIRA> <JIRA.13083656.1498790961854@jira-lw-us.apache.org>
Subject: [jira] [Created] (IGNITE-5627) Web Console: refactor grid columns
 menu
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 30 Jun 2017 02:50:08 -0000

Ilya Borisov created IGNITE-5627:
------------------------------------

             Summary: Web Console: refactor grid columns menu
                 Key: IGNITE-5627
                 URL: https://issues.apache.org/jira/browse/IGNITE-5627
             Project: Ignite
          Issue Type: Sub-task
          Components: UI, wizards
            Reporter: Ilya Borisov
            Assignee: Ilya Borisov
            Priority: Minor


Currently, every menu that allows to toggle individual columns/categories has it's own implementation.

What to do:
1. Create a global reusable component that implements that should:
* Support cases when grid has regular columnDefs only and columnDefs with categories.
* Not display items that are always visible/hidden.
* Have it's own default button markup which can be replaced by transclusion slot.
* Automatically enable groups during previous groupping when user groups by such item (old implementation had such an issue, see admin users list for live example). For example, if first grouping was by column User with column Email hidden, and then user switches to Email grouping, Email column should become visible in grid and should be hidden from menu.
2. Use new component where appropriate and remove old copypasted code.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)