-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
accept int for rows and cols in fig.add_traces
#2410
Comments
Did you close this because it's working now or because you no longer think this is a good idea? |
Because it was fixed by #2451 (sorry for being lazy here!) |
so this is the same as #2391 ? |
ok I got mixed up here. This is not solved by #2391 (more flexible type of int), it's something different (relaxing the iterable constraint). So I'm reopening it... |
Ah ok, thanks for following up :) should #2391 be closed now then? |
@MCBoarder289 if you're interested, solving this issue might involve the same area of the code you were just in :) |
@nicolaskruchten Thanks! I'll take a look and see what I can do here |
Awesome! Please don't feel any pressure to work on it or anything, I was just flagging it in case you were looking for a (possibly easy) entry-point into another PR here :) |
At the moment if you want to add several traces to the same subplot you have to pass an iterable to the
rows
andcols
arguments offig.add_traces
.We could also accept an int here, in which case all traces would be added to the same subplot.
The text was updated successfully, but these errors were encountered: