Skip to content

Conversation

@jenny-s51
Copy link
Contributor

@jenny-s51 jenny-s51 commented Feb 23, 2023

What: Closes #8742. Towards #8005

Moves legacy Table examples into deprecated tab in docs

@patternfly-build
Copy link
Contributor

patternfly-build commented Feb 23, 2023

Copy link
Contributor

@nicolethoen nicolethoen left a comment

Choose a reason for hiding this comment

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

Looks great to me! just one note!

The second is the original `Table` component. It is configuration based and takes a less declarative and more implicit approach about laying out the table structure, such as the rows and cells within it.

**For most common use cases, we recommend using `TableComposable`. Both implementations are supported and fully maintained.**
The legacy `Table` component is configuration-based and takes a less declarative and more implicit approach to laying out the table structure, such as the rows and cells within it.
Copy link
Contributor

Choose a reason for hiding this comment

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

use deprecated rather than legacy in this sentence

Copy link
Contributor

@thatblindgeye thatblindgeye left a comment

Choose a reason for hiding this comment

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

Looks good! Merge conflict just needs to be resolved and a question below based on Nicole's comment

The second is the original `Table` component. It is configuration based and takes a less declarative and more implicit approach about laying out the table structure, such as the rows and cells within it. The documentation for the older table implementation can be found under the [React legacy](/components/table/react-legacy) tab.

**For most common use cases, we recommend using `TableComposable`. Both implementations are supported and fully maintained.**
The documentation for the deprecated legacy table implementation can be found under the [React deprecated](/components/table/react-deprecated) tab. It is configuration based and takes a less declarative and more implicit approach to laying out the table structure, such as the rows and cells within it.
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it also make sense to remove "legacy" from this sentence?

Suggested change
The documentation for the deprecated legacy table implementation can be found under the [React deprecated](/components/table/react-deprecated) tab. It is configuration based and takes a less declarative and more implicit approach to laying out the table structure, such as the rows and cells within it.
The documentation for the deprecated table implementation can be found under the [React deprecated](/components/table/react-deprecated) tab. It is configuration based and takes a less declarative and more implicit approach to laying out the table structure, such as the rows and cells within it.

Possibly a similar question for the "react deprecated" tab's heading of "Legacy Table" as to whether that should be updated to "Deprecated Table".

Copy link
Contributor Author

@jenny-s51 jenny-s51 Feb 28, 2023

Choose a reason for hiding this comment

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

Removed "legacy"!

As far as the heading, ultimately it looks like it makes the most sense to just remove it from both tabs.

When TableComposable is renamed to Table, it won't make much sense to have another "Table" heading nested within the higher-level "Table" heading at the top of the page.

Also since we are communicating in multiple places (the tab, the description, etc.) that the legacy variant is deprecated, we shouldn't need to specify "Deprecated table" again in the heading. Thank you for calling this out - nice catch 🙂 WDYT @thatblindgeye ?

@jenny-s51 jenny-s51 force-pushed the tableDeprecation branch 3 times, most recently from deec918 to 18bf90d Compare February 28, 2023 22:01
Copy link
Contributor

@thatblindgeye thatblindgeye left a comment

Choose a reason for hiding this comment

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

@jenny-s51 in regards to your reply above, that definitely makes sense! Thanks for making the update, only thing is the pf version mismatch needing to be updated again, otherwise looks good!

delete examples from legacy dir

add todo

bump

PR feedback, remove title
@jenny-s51 jenny-s51 requested a review from tlabaj March 2, 2023 19:35
Copy link
Contributor

@tlabaj tlabaj left a comment

Choose a reason for hiding this comment

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

Looks great Jenny!

@nicolethoen nicolethoen merged commit fb6b186 into patternfly:v5 Mar 3, 2023
@patternfly-build
Copy link
Contributor

Your changes have been released in:

  • @patternfly/react-code-editor@5.0.0-alpha.23
  • @patternfly/react-core@5.0.0-alpha.23
  • @patternfly/react-docs@6.0.0-alpha.26
  • demo-app-ts@5.0.0-alpha.6
  • @patternfly/react-table@5.0.0-alpha.23

Thanks for your contribution! 🎉

@jenny-s51 jenny-s51 deleted the tableDeprecation branch March 9, 2023 20:10
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.

Move legacy examples to "React deprecated" tab

5 participants