This version removes C# interop from the core F# Plotly.NET library, offloading those implementations directly to the native C# lib Plotly.NET.CSharp:
Milestone link with all the fixed/closed issues
Maintenance release to prevent Plotly.NET breaking for users that upgrade the DynamicObj dependency to >=3.0.0. DynamicObj is now pinned to the version range [2.0.0, 3.0.0) until we manage to make Plotly.NET work with the major changes in that lib.
Major release with lots of bug fixes, improvements, and upstream feature additions from plotly.js. Many changes are backwards-incompatible with previous versions.
Milestone link with all the fixed/closed issues
-
Add Chart.Pareto. This contribution started with the fslab hackathon 2023 and was submitted by @rockfaith75 and @smoothdeveloper, thank you!
-
Make Contours setting directly accessible on all supported traces, fixes #426
-
Allow DynamicObj for the args properties of update buttons, fixes #414
-
Expand DisplayOptions to include direct fields for document title, description, charset, and favicon, fixes #374
-
Keep up with plotlyjs 2.x incremental updates. Note that v2.28+ will be on Plotly.NET 6.0, as some major changes are needed for supporting it properly (see #441)
- v2.22:
- v2.23:
- v2.24:
- v2.25:
- v2.26:
- v2.27:
Additional extension package releases::
- Plotly.NET.ImageExport (5.0.1 -> 6.0.0)
- Plotly.NET.Interactive (4.2.0 -> 5.0.0)
- Plotly.NET.CSharp (0.11.1 -> 0.12.0)
This release makes Plotly.NET compatible with LINQPad.
Read more about this on the respective pull request.
Thanks a lot to @Peter-B-.
This is a maintenance release that aims to keep up with plotlyjs 2.x incremental updates.
The only major change is the usage of Giraffe.ViewEngine.StrongName instead of Giraffe.ViewEngine as html dsl. This could be considered as a breaking change, but it's not because the Giraffe.ViewEngine.StrongName package is a drop-in replacement for Giraffe.ViewEngine with the only difference being a signed assembly
-
Keep up with plotlyjs 2.x incremental updates:
- v2.22+ will be on Plotly.NET 5.0, because it introduces breaking changes.
- v2.21:
- v2.20:
- v2.19:
-
misc fixes and improvements:
Additional extension package releases::
- Plotly.NET.ImageExport (4.0.0 -> 5.0.0)
- Plotly.NET.Interactive (4.1.0 -> 4.2.0)
- Plotly.NET.CSharp (0.10.0 -> 0.11.0)
Milestone link with all the fixed/closed issues
-
Add high level arg for base layer style to all mapbox charts
-
Add ShowXAxisRangeSlider argument for Chart.OHLC and Chart.Candlestick
-
Refactor DisplayOptions - An object to control the way Charts are displayed in generated HTML files:
- Add various functions to manipulate DisplayOptions, Refactor DisplayOptions as DynamicObj (again)
- Add
PlotlyJSReferencetype and logic to handle various ways of referencing plotly.js in HTML output:Full: Include the full plotly.js source code. The currently supported plotly.js version is now included as embedded resource in the package. HTML files using this option are self-contained and can be used offline.CDN: The default. uses a script tag in the head of the generated HTML to load plotly.js from a CDN.Require: Use requirejs to load plotly. This option is now used in Plotly.NET.Interactive. Unnecessary usage of require.js is now removed from all other options but this.NoReference: Don't include any plotly.js reference. Useful if you want to embed the output into another page that already references plotly.
-
Keep up with plotlyjs 2.x incremental updates:
- v2.18:
- v2.17:
- v2.16:
- v2.15:
- v2.14:
- v2.13:
- v2.12:
- v2.10:
- v2.9:
- v2.8:
Minor fixes for Object abstractions:
- Use correct Optional Parameter Attributes everywhere. This affects object abstractions for the following objects, but should be backwards compatible:
- Annotation
- LayoutImage
- Pattern
- TableCells
FontSelectionStyle.initnow correctly returns a FontSelectionStyle instead of unit
This release adopts strong assembly naming. This might cause backwards incompatibility and therefore results in an early major version increase. For more insights why we do this, check out the conversation on this issue
Other additions: