Page MenuHomePhabricator

Sort key in Template Output
Closed, DeclinedPublic

Description

Author: dasch

Description:
when creating an Output for a template there should be also created a SortKey so it also can be used in costum sortable tables, at the Moment propertys with untis are not sorted correctly


Version: unspecified
Severity: enhancement

Details

Reference
bz13318

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 10:05 PM
bzimport set Reference to bz13318.

dasch wrote:

it's really annoying when i Create a sortable table with number an they are sorted like string. I think it should not ne that difficult to put a sortkey befor the output. It's online putting the number filled with 0 in front into a div with style="display:none"

dasch wrote:

in the table output the same thing is used, so there should not be any problem with transfering this thing from the table to the template output

Re-assign to extension developer for triage/comments.

DaSch, what you suggest would add hidden HTML to values that are passed to templates. Doing this in general would break tempaltes that expect plain values. Also, there is currently no proper support for using SMW sorting tables directly without #ask. CSS and JavaScript needed for that feature are inserted only on-demand if an SMW function needs them (e.g. because the page also has anther query or factbox).

Maybe there should be template= support for tables. But this would require to fix a syntax that would be used in these tempaltes (piped or HTML).

Seeing no reply to my earlier comment, there is still no viable proposal to implement this feature request without breaking existing functions. Clearly, not introducing new bugs is more important than adding new features, so I have to close this without action, at least for now. We can re-open it if there is a workable proposal.

In fact, if someone could finally come up with a proposal how to pass parameters to single ?printouts (e.g. limit), then this could be controlled and the requested behaviour could become an optional feature. But it is not possible to have that as a general behaviour for all cases.

Changing all WONTFIX high priority bugs to lowest priority (no mail should be generated since I turned it off for this.)