Skip to content
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

Track row actions output on each row to catch cases where custom output ... #58

Closed
wants to merge 1 commit into from

Conversation

jeremyfelt
Copy link
Contributor

...may not be added

When a provider class does not provide a method to output one of its registered columns, our list table should account for the possible lack of row actions.

This commit adds a tracking property for the display of row actions. If a column's output is not handled by the provider class and row actions have not yet been displayed, we handle output of the row actions. Once row actions have been output once, the flag is maintained throughout the row. When the row is complete, the flag is reset for the next.

One quirk - if a provider class handles the output for the first column, but does not handle row actions, and does not handle the output for the next column, row actions will be output in that second column. This feels a little weird, but I think gets us close enough.

Fixes #51

…ut may not be added

When a provider class does not provide a method to output one of its registered columns, our list table should account for the possible lack of row actions.

This commit adds a tracking property for the display of row actions. If a column's output is not handled by the provider class and row actions have not yet been displayed, we handle output of the row actions. Once row actions have been output once, the flag is maintained throughout the row. When the row is complete, the flag is reset for the next.

One quirk - if a provider class handles the output for the first column, but does not handle row actions, and does not handle the output for the next column, row actions will be output in that second column. This feels a little weird, but I think gets us close enough.

Fixes #51
@jeremyfelt
Copy link
Contributor Author

This is probably what we want, but should get a second look - @danielbachhuber @rinatkhaziev

@rinatkhaziev
Copy link
Contributor

This is one hell of a commit message 👍

@rinatkhaziev
Copy link
Contributor

Will take a look in the AM, too dumb right now

@ghost ghost assigned jeremyfelt Mar 6, 2013
@danielbachhuber
Copy link
Contributor

I'm going to punt this to 0.5-early, so we aren't merging things into v0.4 at the last minute.

@jeremyfelt jeremyfelt closed this Apr 22, 2014
@jeremyfelt jeremyfelt removed their assignment Apr 22, 2014
@GaryJones GaryJones modified the milestones: 0.5.0, Future Release Mar 14, 2022
@GaryJones GaryJones deleted the always-row-action branch September 9, 2023 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make sure that the first column after the checkbox in the table view displays row actions
4 participants