qlik-oss / sn-pivot-table Goto Github PK

When we are trying to embed the QLIK visuals using sn-pivot-table , colour codes for the cell are not reflecting in our application where as present in the QLIK. Any help would be appreciated.

The stardust peer dependency should be set to minimun version OR higher, to avoid errors/warnings when we update @nebula.js/stardust.

  "peerDependencies": {
    "@nebula.js/stardust": ">=3.3.0"
  }

Hello,

We are migrating our mashups from Capabilities API to Nebula.JS, we are using the visualizations from Nebula. The versions of our packages are those:

• "@nebula.js/stardust": "^3.0.4"
• "@nebula.js/sn-table": "^1.19.1"
• "@nebula.js/sn-bar-chart": "^1.25.0"
• "@nebula.js/sn-line-chart": "^1.20.0"
• "@nebula.js/sn-combo-chart": "^1.19.6"
• "@nebula.js/sn-pivot-table": "^1.0.1"
• "@nebula.js/sn-scatter-plot": "^3.32.0"

We are not rendering the visualizations on the fly, we are using the id from Qlik to render existing master objects. All the visualizations are working fine except the pivot-table, which we are not able to render and no errors are displaying.

Can you give us some help? We also tried it using stardust 2.x version and is not working.

Thanks,
Pau Garrido

When taking a snapshot and later consuming it, the snapshot should look near identical to when the snapshot was created.

This is not the case today, as sometimes the scroll position is slightly off and may even show 1 row/column "off". When taking a snapshot all data is available, this is not the case when consuming it, as only the data in "view" is available than. A possible solution is to try and compute the scroll offset of the first row/column when taking the snapshot and then apply that offset when consuming it.

When an error occur while fetching data is just swallowed and logged. But no information is given to the user. This can probably be improved UX wise.

By changing font size to a large size, it is possible to render text which is too large for the default row height (28 px) to handle.

This should be changed so that the row height is a minimum 28 px but does scale up with the font size.

When you have a pseudo dimension and measure header/s that have large amount of space to render on. You can scroll so that the headers disappears. They should be sticky and always visiable, even when the user scrolls.

We are having some issues with the dimension columns being way too small to be readable. We could possibly set a minimum limit for the columns inside our forked package we use, but this would necessarily affect all of the columns, which is not desired. We were thinking that it would be a great feature if the columns width would be draggable (like for example in Excel).
That leads me to a question - is something like this by any change in your scope for development in the upcoming months?