Webstaff grid could be smarter in IDL mode
Bug #1683385 reported by
Mike Rylander
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned | ||
3.3 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The grid we've built for general use in the web staff client has a mode where it auto-configures columns based on a named IDL class. This is great!
However, if you need to add specialized columns (such as for linking barcodes or formatting timestamps) then you get extra "raw" versions of those columns in the column picker. It would be a kindness if the grid would notice that a path has been used explicitly and skip the column addition.
The wildcard syntax for column addition knows how to do this, so hopefully that code can be cribbed.
tags: | added: webstaffclient |
tags: | added: webstaffcolumns |
tags: | added: needsdiscussion |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
Changed in evergreen: | |
milestone: | 3.3.2 → 3.3.3 |
Changed in evergreen: | |
milestone: | 3.3.3 → 3.4-beta1 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As I look at bug 1669866, bug 1722387 and bug 1705133, it might be a good idea to consider whether it is indeed a good thing to configure columns based on a named IDL class. Is this the reasons why we are getting very long column pickers in some interfaces that include data that will rarely be used? Would it be better to explicitly add all columns rather than adding an entire class at one time?