-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Enable Row Selection on Plugin Table Component #2856
Conversation
But how do you grab the selected rows for further operations? Is a test possible for this? Thanks! |
You can see an example of its intended usage in my VO plugin here: https://github.com/duytnguyendtn/SkyviewJdaviz/blob/pyvo/pyvo_plugin/pyvo.py#L128-L141, but in short, you access it via the
The only programmatic way I know of selecting the rows is by setting |
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 simple enough to me - thanks! I'm not really sure there is a way to test this until there is an actual use-case either. If we're worried we may not have a use-case, we could let this sit unmerged until there is one and then add test coverage there 🤷♂️
- Plugin Table components now support row selection. [#2856] | ||
|
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.
since this isn't actually used anywhere, it might not need a changelog entry?
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.
Entirely up to y'all, just need the instruction and I can remove 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.
Since people can use this downstream, let's keep it.
My understanding is that Duy would use this downstream, no? |
Yes, I'll be using this downstream. The Virtual Observatory plugin will be it's own PR, but I could build that PR on top of this one. I mainly tried to break up the effort to make it easier for reviews. Entirely up to y'all how you'd like to proceed. |
I have no objection to merging myself - this is pretty isolated and would be pretty easy to strip back out if for some reason it goes unused (which seems unlikely). @duytnguyendtn - can you please make a note to try to add test coverage for this capability in the eventual PR that makes use of 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.
Kyle, feel free to merge when that extra comment you asked for is added. Thanks, all!
- Plugin Table components now support row selection. [#2856] | ||
|
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.
Since people can use this downstream, let's keep it.
# NOTE: These UI features are not covered in test coverage. Plugins making use of | ||
# this feature should ensure test coverage for their respective tables. |
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.
Added a note regarding test coverage here. Thanks!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2856 +/- ##
==========================================
- Coverage 88.90% 88.71% -0.20%
==========================================
Files 111 111
Lines 17148 17113 -35
==========================================
- Hits 15246 15181 -65
- Misses 1902 1932 +30 ☔ View full report in Codecov by Sentry. |
Description
Hello Jdaviz Team!
This PR is a small change to the Plugin Table component to expose the Vuetify row selection attributes for the Virtual Observatory plugin I'm working on. Because this is a frontend component, no new tests were added. A changelog entry will follow the publication of this PR, once a PR number is assigned.
It was great to sync my fork again :)
Change log entry
CHANGES.rst
? If you want to avoid merge conflicts,list the proposed change log here for review and add to
CHANGES.rst
before merge. If no, maintainershould add a
no-changelog-entry-needed
label.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
trivial
label.