Skip to content

Commit e3a4e23

Browse files
Merge branch 'master' of ssh://github.com/MetalBlueberry/go-plotly
2 parents 460c150 + 3fa2af4 commit e3a4e23

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ package main
2020

2121
import (
2222
grob "github.com/MetalBlueberry/go-plotly/graph_objects"
23-
"github.com/MetalBlueberry/go-plotly/plotly"
23+
"github.com/MetalBlueberry/go-plotly/offline"
2424
)
2525

2626
func main() {
@@ -107,4 +107,4 @@ For bool, the solution is as simple as defining the types again inside graph_obj
107107

108108
For strings... This is a little bit more complicated, In AWS package they are using `aws.String` which maps to `*string` to workaround this issue, but I find that really annoying because you have to wrap every single string with `aws.String("whatever")`. For now I've decided to define the type String but leave it as `interface{}` instead of `*string` to allow you to use raw strings. The draw back is that you can pass any value of your choice... Hopefully you can live with this :).
109109

110-
For numbers... It's similar to strings, Right now you cannot create plots with integer/float numbers with 0 value. I've only encounter problems when trying to remove the margin and can be workaround with an small value like `0.001`. I would like to avoid using interface{} or defining types again to keep the package interface as simple as possible.
110+
For numbers... It's similar to strings, Right now you cannot create plots with integer/float numbers with 0 value. I've only encounter problems when trying to remove the margin and can be workaround with an small value like `0.001`. I would like to avoid using interface{} or defining types again to keep the package interface as simple as possible.

0 commit comments

Comments
 (0)