-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Overview documentation overhaul #1681
Conversation
fb8cca5
to
5d556d4
Compare
5d556d4
to
441ee67
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a really great improvement!
- :meth:`web3.eth.uninstallFilter() <web3.eth.Eth.uninstallFilter>` | ||
- :meth:`web3.eth.getLogs() <web3.eth.Eth.getLogs>` | ||
- :meth:`Contract.events.your_event_name.createFilter() <web3.contract.Contract.events.your_event_name.createFilter>` | ||
- :meth:`Contract.events.your_event_name.build_filter() <web3.contract.Contract.events.your_event_name.build_filter>` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe also add your_event.processReceipt
, your_event.processLog
, your_event.getLogs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a small ticket worth of work to add a getLogs
method to the events documentation, plus sort out links for processLog
and processReceipt
. The latter two get lumped under the same top-level link without links of their own (ContractEvents.myEvent). Will look to sort that out in a subsequent PR, so I can start this beta release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just did a quick scan of the overview page, but based on that it looks great!
What was wrong?
The existing Overview documentation provides an introduction to Providers, then dumps out the base class API, e.g., utility methods for type conversions, address helpers, etc.
How was it fixed?
I thought the Overview page would be put to better use (i.e., answer more typical support questions) if it instead gave a tour of the features in the lib. I believe this will be useful for orienting newcomers, but I also built the reference page I wished existed; I included much of the API, broken into usage category.
There's a lot of content and its a big departure from the current state of things. Feedback appreciated!
Generated docs preview: https://web3py--1681.org.readthedocs.build/en/1681/
Todo:
Cute Animal Picture