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
feat: track and expose non-persistent views #843
feat: track and expose non-persistent views #843
Conversation
I think if there's TODOs, this PR should be a draft |
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 breaking change based on the removal of persistent_views
, do we want to keep it instead but add a deprecation warning for future removal?
Missed the view store line, ignore this
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.
Untested, lgtm
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.
untested
Summary
This PR adds functionality to track and expose non-persistent views to the user. The user can manually add views to be tracked via
Client.add_view
and can retrieve all non-persistent views viaClient.views
.Closes #14.
Checklist
task pyright
and fixed the relevant issues.