Skip to content

areaType->summaryType

Choose a tag to compare

View all tags
@emeeks emeeks released this 28 Feb 19:17
v1.17.0
5591ce5

I was expecting to do the next minor version bump when the docs release and Semiotic gets moved into the nteract org (which should happen next week) but this last batch of changes was just too much, and I don't want to gatekeep it, so 1.18.0 will have to be the nteract release. This one has quite a few things:

#CHANGES

  • A few versions back, areas in XYFrame was renamed summaries (though it's all backward compatible under the hood) but there were still computed class names and other bits that still said area that now say summary
  • oSort replaces sortO in OrdinalFrame

FEATURES

  • custom hover behavior in ordinal frame passes summary props, like boxplot points (thanks @torioLuz!)
  • FacetController now supports arrays of hoverAnnotation or pieceHoverAnnotation just like the regular frames
  • minimap in MinimapXYFrame now inherits style, class and render props from the parent frame
  • area nodes (like sankey and dagre nodes) in NetworkFrame now have a zoomedWidth and zoomedHeight to reflect their zoomed size
  • OrdinalFrame accepts an axes prop like XYFrame
  • brush extent is always returned sorted so that the y values are [min, max].

FIXES

  • column-hover in OrdinalFrame now passes proper screenCoordinates if you want your own html annotation based on that
  • FacetController wasn't always updating the extents properly if you deleted a frame or only changed data in one of your frames or swapped out all your frames for new ones
  • FacetController was duplicating annotations on the hovered frame
  • NetworkFrame was duping nodes that were sent in as object references of edge source-target keys
  • Network data sometimes was being mutated so you would see weird effects on your frames if you used the same data in multiple frames
  • All the custom generators (customPointMark, customNodeIcon, customMark, etc) should be sent the same kind of data in the same pattern (obviously with scales and frame-specific stuff being different in different frames)
  • display names for spark frames match up with the component names
Assets 2
Loading