Skip to content

Creating and updating figures section #26

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

Merged
merged 19 commits into from
Jun 27, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
class-style property access
  • Loading branch information
jonmmease committed Jun 22, 2019
commit c0f6c8c8a91aee69482692a3b8e64bbb415429b5
3 changes: 2 additions & 1 deletion notebooks/creating-updating-figures.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,8 @@ As an alternative to working with Python dictionaries, plotly.py provides a hier

1. Graph objects provide precise data validation. So if you provide an invalid property name or an invalid property value, an exception will be raised with a helpful error message describing the problem.
2. Graph objects contain descriptions of each property as Python docstrings. You can use these docstrings to learn about the available properties as an alternative to consulting the *Full Reference*.
3. Graph objects support higher-level convenience functions for making updates to already constructed figures, as described below.
3. Properties of graph objects can be accessed using dictionary-style key lookup (e.g. `fig["layout"]`) or class-style property access (e.g. `fig.layout`).
4. Graph objects support higher-level convenience functions for making updates to already constructed figures, as described below.

Graph objects are stored in a hierarchy of modules under the `plotly.graph_objects` package. Here is an example of one way that the figure above could be constructed using graph objects.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it important for users (as opposed to devs) to mention the "hierarchy of modules"? How about "stored under the ... package"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only insofar as it's important that people look for go.layout.title.Font() and don't expect to find go.Font().


Expand Down