Bump Plotly.NET from 2.0.0-preview.6 to 2.0.0

[dependabot]

Bumps Plotly.NET from 2.0.0-preview.6 to 2.0.0.

Release notes

Sourced from Plotly.NET's releases.

2.0.0

Plotly.NET 2.0

Plotly.NET finally has reached all milestones for 2.0 and is ready for a stable release.

This release is the culmination of almost 2 years of work in >500 commits by 17 contributors.

Here is an attempt to visualize the history of these changes in a few seconds:

(made with gource)

All APIs have changed significantly - this release is incompatible with 1.x and many 2.x-preview/beta versions.

TL;DR

• All plotly chart/trace types!
• Unified API!
• chart rendering in notebooks!
• programmatic static image export!
• Exhaustive docs!
• We have a discord server, feel free to ask questions there!

Core library

General

• The API layer model has refined and used for every type of plotly object abstraction. In brief,
  • There are 5 main categories of abstractions: Trace (chart data and type), Layout(non-data chart styling), Config(render options), DisplayOptions(html display options), StyleParam(DSL for styling options)
  • Many properties used in these levels are themselves objects, which are in the respective *Objects namespace (e.g. Geo, which determines map layout of geo traces is an object on the Layout and therefore in the LaoutObjects namespace.)
  • every object is based on DynamicObj and its properties can therefore be further customised by dynamic member assignment. Therefore, every plotly property can be set manually, even those which do not have direct abstractions.
• There are now several Trace types for each kind of subplot (Trace2D, Trace3D, etc.) and eqivalent Chart types (Chart2D, Chart3D, etc). while not visible from the top level api (everything kan be accessed via the unified Chart API), this greatly improves correct multi chart layouting.
• There are 3 ways of creating charts with increasing level of customization:
  1. The Chart API as a unified API surface for chart creation and styling
     • Chart.<ChartType> (e.g. Chart.Point) for chart creation from data and some chart specific styling options
     • Chart.with<Style or object> (e.g. Chart.withXAxisStyle) for styling of chart objects
  2. Creation of Chart objects by manually creating Trace, Layout and Config objects with many more optional customization parameters
  3. Exclusive usage of DynamicObj - you can translate any plotly.js javascript with this method.

Chart/Trace abstractions

You can create the following Charts with Plotly.NET's API (and many more by combining them):

• Cartesian 2D (Chart2D):
  • Scatter (Point, Line, Spline, Bubble, Range, Area, SplineArea, StackedArea)
  • Funnel
  • Waterfall
  • Bar (Bar, Column, StackedBar, StackedColumn)
  • Histogram

... (truncated)

Changelog

Sourced from Plotly.NET's changelog.

2.0.0 - Apr 24 2022

Plotly.NET finally has reached all milestones for 2.0 and is ready for a stable release.

This release is the culmination of almost 2 years of work in >500 commits by 17 contributors.

Here is an attempt to visualize the history of these changes in a few seconds:

(made with gource)

All APIs have changed significantly - this release is incompatible with 1.x and many 2.x-preview/beta versions.

TL;DR

• All plotly chart/trace types!
• Unified API!
• chart rendering in notebooks!
• programmatic static image export!
• Exhaustive docs!
• We have a discord server, feel free to ask questions there!

Core library

General

• The API layer model has refined and used for every type of plotly object abstraction. In brief,
  • There are 5 main categories of abstractions: Trace (chart data and type), Layout(non-data chart styling), Config(render options), DisplayOptions(html display options), StyleParam(DSL for styling options)
  • Many properties used in these levels are themselves objects, which are in the respective *Objects namespace (e.g. Geo, which determines map layout of geo traces is an object on the Layout and therefore in the LaoutObjects namespace.)
  • every object is based on DynamicObj and its properties can therefore be further customised by dynamic member assignment. Therefore, every plotly property can be set manually, even those which do not have direct abstractions.
• There are now several Trace types for each kind of subplot (Trace2D, Trace3D, etc.) and eqivalent Chart types (Chart2D, Chart3D, etc). while not visible from the top level api (everything kan be accessed via the unified Chart API), this greatly improves correct multi chart layouting.
• There are 3 ways of creating charts with increasing level of customization:
  1. The Chart API as a unified API surface for chart creation and styling
     • Chart.<ChartType> (e.g. Chart.Point) for chart creation from data and some chart specific styling options
     • Chart.with<Style or object> (e.g. Chart.withXAxisStyle) for styling of chart objects
  2. Creation of Chart objects by manually creating Trace, Layout and Config objects with many more optional customization parameters
  3. Exclusive usage of DynamicObj - you can translate any plotly.js javascript with this method.

Chart/Trace abstractions

You can create the following Charts with Plotly.NET's API (and many more by combining them):

• Cartesian 2D (Chart2D):
  • Scatter (Point, Line, Spline, Bubble, Range, Area, SplineArea, StackedArea)
  • Funnel
  • Waterfall
  • Bar (Bar, Column, StackedBar, StackedColumn)
  • Histogram
  • Histogram2D

... (truncated)

Commits

• 863ce02 use correct nuget key env variable
• 3dca9f4 Bump release notes
• 7121b4d apply formatting
• 9491ce7 Fix notebook display ommitting chart description
• b0ad27d Add contributor images to readme
• dc7091b add verify docs target
• 5c6f359 fix formatting and formatting build tasks
• fec9a3b update remaining gh actions
• db8a393 upgrade to .net 6, move to project-based build pipeline
• 6fec834 Update README.md
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #28.