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

[core] fix(Portal): handle more className edge cases #4729

Merged
merged 1 commit into from
May 20, 2021

Conversation

jkillian
Copy link
Contributor

Fixes #4519, #4728

Checklist

  • Includes tests
  • Update documentation

Changes proposed in this pull request:

Updates how Portal removes classes so that it will not crash when 1) an empty string was previously provided or 2) when removing multiple classes at once.

Reviewers should focus on:

Any logic errors in removing the class names.

@jkillian jkillian changed the title make portal classname removal more robust Fix various crashes possible when using Portal component className May 20, 2021
Copy link
Contributor

@adidahiya adidahiya left a comment

Choose a reason for hiding this comment

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

thanks @jkillian!

@adidahiya adidahiya changed the title Fix various crashes possible when using Portal component className [core] fix(Portal): handle more className edge cases May 20, 2021
@adidahiya adidahiya merged commit 77c259f into palantir:develop May 20, 2021
@jkillian
Copy link
Contributor Author

👋 😄

@jkillian jkillian deleted the jk/fix-portal-classname branch May 20, 2021 21:35
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.

portalClassName breaks with empty string
2 participants