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

refactor(): remove [main] from split-pane #19511

Merged
merged 1 commit into from Oct 2, 2019
Merged

refactor(): remove [main] from split-pane #19511

merged 1 commit into from Oct 2, 2019

Conversation

liamdebeasi
Copy link
Contributor

@liamdebeasi liamdebeasi commented Oct 1, 2019

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Build (npm run build) was run locally and any changes were pushed
  • Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

Split pane allows currently allows users to place the main attribute on their content for the split pane to find.

What is the new behavior?

Users should use the contentId prop to help split pane find its main content

Does this introduce a breaking change?

  • Yes
  • No

Other information

@liamdebeasi liamdebeasi marked this pull request as ready for review October 1, 2019 14:00
@brandyscarney
Copy link
Member

Did we not have deprecation warnings for this?

@liamdebeasi
Copy link
Contributor Author

No, I don't think there was ever a deprecation warning for this.

@liamdebeasi liamdebeasi merged commit 02d7841 into next Oct 2, 2019
@liamdebeasi liamdebeasi deleted the split-main branch October 2, 2019 14:42
@brandyscarney
Copy link
Member

This needs to be updated to include removing the newly added deprecation warning: #19237

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.

None yet

2 participants