Skip to content

Conversation

@maxceem
Copy link
Collaborator

@maxceem maxceem commented Jul 25, 2019

fix rendering DraftJS message when block doesn't have inline content

Fix for the issue with rendering > in DraftJS.

The root of the issue is that in code we create a block first, and after when we find inline content inside that block we set some properties of the block like text. But if there is no inline content, then such properties of the block stay unutilized which causes an error later as a block is not fully defined.

So the solution is set the default values of properties for the block as it has empty inline content. And if there is some inline content, such properties would be updated.

@vikasrohit vikasrohit merged commit 875eac1 into master Jul 25, 2019
@vikasrohit
Copy link

@maxceem the strange thing is that why this issue started to appear only after our recent release. The message which has this problem was created on Jun 24, so it should have appeared before our release as well.

@vikasrohit
Copy link

Also, could you please log a ticket and update your investigation results there.

@maxceem
Copy link
Collaborator Author

maxceem commented Jul 25, 2019

@maxceem the strange thing is that why this issue started to appear only after our recent release. The message which has this problem was created on Jun 24, so it should have appeared before our release as well.

That is strange, but so far I don't see any reason how it could happen only after the release but not before.

Also, could you please log a ticket and update your investigation results there.

Created #3219

@vikasrohit vikasrohit deleted the hotfix/post-release-2.4.13.7 branch September 18, 2019 04:57
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