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

Progress: Variable column widths #21600

Merged
merged 4 commits into from Apr 2, 2018
Merged

Progress: Variable column widths #21600

merged 4 commits into from Apr 2, 2018

Conversation

Erin007
Copy link
Contributor

@Erin007 Erin007 commented Apr 2, 2018

This PR is confirmation that Virtualized MultiGrid allows us to have variable column widths. I pass in a hardcoded list of widths to a getColumnWidths function; in the future the width of the column will be based on the number of levels in the lesson. I also hardcoded a list of filler data to be passed to the Multigrid so it starts to show info more in line with what will really be shown in the table.

In this PR, I also reworked the styles and helper functions to be more consistent with format of other components in our codebase.

screen shot 2018-04-02 at 11 00 15 am

Copy link
Contributor

@caleybrock caleybrock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really cool.

At this point are there other standing concerns to stop us from fully moving forward with react-virtualized? To me it seems like this component will everything we need.

@Erin007
Copy link
Contributor Author

Erin007 commented Apr 2, 2018

My only lingering concern is around the ability to sort. It's not part of the initial work but something Poorva definitely wants in revisions. Looks like it's possible: bvaughn/react-virtualized#650, but I haven't tried to implement it yet.

@caleybrock
Copy link
Contributor

Good point. I think it's possible, and it'll probably be expensive to sort and re-render so we'll likely need to build some customization into it anyways.

I also have a feeling we'll have to build a second version of these tables without any css, just for the purpose of printing. I know that's a V2, but it's something to think about, especially if it means maintaining two tables.

@Erin007 Erin007 merged commit 37b3323 into staging Apr 2, 2018
@Erin007 Erin007 deleted the variable-column-widths branch April 2, 2018 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants