You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is currently possible to define style expressions at the kpi level.
Eg: 'some style' if profit < 0 else 'some other style'.
That works fine for reports where the only difference between columns is the time period.
For reports made possible in version 3 where columns are more specialized, it makes sense to have style expressions apply at the column level (eg to apply something such as 'red' if cell_val < 0 else ''.
Such generic style expressions should be defined on styles (so one can define styles such as red if negative), and then applied at the column level with the implementation of #14.
The text was updated successfully, but these errors were encountered:
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.
sbidoul
added
no stale
Use this label to prevent the automated stale action from closing this PR/Issue.
and removed
stale
PR/Issue without recent activity, it'll be soon closed automatically.
labels
Dec 26, 2021
It is currently possible to define style expressions at the kpi level.
Eg:
'some style' if profit < 0 else 'some other style'
.That works fine for reports where the only difference between columns is the time period.
For reports made possible in version 3 where columns are more specialized, it makes sense to have style expressions apply at the column level (eg to apply something such as
'red' if cell_val < 0 else ''
.Such generic style expressions should be defined on styles (so one can define styles such as
red if negative
), and then applied at the column level with the implementation of #14.The text was updated successfully, but these errors were encountered: