-
Notifications
You must be signed in to change notification settings - Fork 15
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
docs: use_render_queue, use_liveness_scope, use_table_listener docs #1044
Conversation
mofojed
commented
Nov 26, 2024
- Adding some more missing hooks documentation
- Closes docs: use_liveness_scope #823, closes deephaven.ui hooks documentation #659
- Adding some more missing hooks documentation - Closes deephaven#823, closes deephaven#659
- Remove the API reference to use_render_queue. The autodoc doesn't work correctly if the function has no parameters - Remove redundant information from the README at the base - Update signature for use_table_listener
Co-authored-by: margaretkennedy <[email protected]>
Co-authored-by: margaretkennedy <[email protected]>
- Specify list or dict for the row_data vs row_list methods - Add link to toast - Add warning in the use_table_listener hook intro paragraph
Co-authored-by: margaretkennedy <[email protected]>
- There was already a note in the introduction for the only recommendation we were providing
@@ -0,0 +1,62 @@ | |||
# use_liveness_scope |
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.
Question for @dsmmcken: When Salmon goes live, will these headings have to change the docs syntax:
---
id: whatever
title: whatever
sidebar_label: ...
---
And if so, is there a transition tool that will make changing them quick?
|
||
## Refactoring to avoid liveness scope | ||
|
||
In the above example, we could refactor the component to avoid using `use_liveness_scope` by deriving the table from state instead of setting it directly: |
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.
Which is the better approach? If this is better than using a liveness scope, then why present the first example at all?
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.
It's kind of an escape hatch if you need it. Ideally you refactor such that you don't need to use it.
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.
Two overarching comments:
- Link to other docs (
use_state
,toast
, etc.) every time you mention a method in backticks. - Some images or GIFs would be greatly beneficial to these docs, so I could actually see what happens without having to start up a server myself to run code.
- The empty set seemed to be an odd choice. Default to `None` for the table data hooks.
- Add explanation for sentinel object - Add examples with null value
Co-authored-by: JJ Brosnan <[email protected]>
@jnumainville I noticed the docs failing when I try to autodoc the |
- it's failing, ticket filed https://deephaven.atlassian.net/browse/DH-18247
20179a0