Switch from wcharczuk/go-chart to go-analyze/charts #207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I have been maintaining a fork of the now-archived wcharczuk/go-chart for over a year.
Since the fork, there have been minimal changes to the original
wcharczuk/go-chart
code, now maintained as thechartdraw
package. Merging this PR should not change how your charts look or behave, but ensures you depend on an actively supported module.Most development has focused on a new API and chart style in the root
charts
package (see feature examples). If you want to explore that, I’d be happy to help; if not,chartdraw
remains stable and supported.We’re preparing for
v0.6.0
and would value any feedback on the rootcharts
API (chartdraw
will remain stable). Thank you for considering.