Skip to content

fix(tables): update reactabular-table, fix provider renderers prop - #357

Merged
jeff-phillips-18 merged 1 commit into
patternfly:masterfrom
priley86:reactabular-table
May 16, 2018
Merged

jeff-phillips-18 merged 1 commit into
patternfly:masterfrom
priley86:reactabular-table

Conversation

@priley86

Copy link
Copy Markdown
Member

affects: patternfly-react

What:
The reactabular-table dependency recently caused a breaking change to our Table.PfProvider component. The components prop has been changed to renderers and the backported components prop no longer renders our tables at runtime. This was causing the deployed storybook tables to fail.

The components prop will be deprecated in future versions it seems.

Link to Storybook:
https://rawgit.com/priley86/patternfly-react/reactabular-table-storybook/index.html

Additional issues:
Relates to #348

@coveralls

Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 1367

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 74.086%

Totals Coverage Status
Change from base Build 1359: 0.0%
Covered Lines: 1704
Relevant Lines: 2103

💛 - Coveralls

@jeff-phillips-18

Copy link
Copy Markdown
Member

bad reactabular-table for breaking in a minor release!

Refactor - Rename components field to renderers. 
The old prop name will be dropped in the next major version although it works for now.

if that is true, why did it break us?

@priley86

Copy link
Copy Markdown
Member Author

i think it is false 🤣. components seems unsupported now w/ production builds.

i filed an issue upstream: reactabular/reactabular#348

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.

3 participants