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

fix(localized-rich-text-input): make behaviour match other localized component #1108

Merged
merged 1 commit into from
Oct 17, 2019

Conversation

montezume
Copy link
Contributor

Summary

Make behaviour of LocalizedRichTextInput match other LocalizedMutilineTextInput as per the expand / collapse states.

@@ -20,8 +20,8 @@ const Input = props => {
return (
<LocalizedRichTextInput
value={{
en: LocalizedRichTextInput.deserialize(''),
Copy link
Contributor Author

Choose a reason for hiding this comment

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

forgot to remove these before

@@ -225,10 +225,6 @@ LocalizedRichTextInput.propTypes = {
onClickExpand: requiredIf(PropTypes.func, props => props.showExpandIcon),
};

LocalizedRichTextInput.serialize = RichTextInput.serialize;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

forgot to remove

@@ -117,7 +117,7 @@ class RichTextInput extends React.PureComponent {
// expand all multiline language inputs in case the
// first one was expanded when all languages
// are shown
if (!this.props.isCollapsed) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this prop didn't exist 🤦‍♂

@montezume montezume self-assigned this Oct 17, 2019
@kodiakhq kodiakhq bot merged commit 3de26c5 into master Oct 17, 2019
@kodiakhq kodiakhq bot deleted the ml-fix-rti branch October 17, 2019 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants