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

Remove json parsing #1

Open
wants to merge 32 commits into
base: master
Choose a base branch
from
Open

Remove json parsing #1

wants to merge 32 commits into from

Conversation

buob
Copy link

@buob buob commented Feb 7, 2019

This solves a couple problems:

  1. Poison was pretty out of date (so trying to use the lib caused
    version conflicts with the version we were already using in our app)

  2. Our draftjs content wasn't stored as a string, it was stored as a
    map. Removing json parsing will let the user parse it if they need
    to (in whatever way they want), and let those who don't need to use
    it out of the box.

This solves a couple problems:

1. Poison was pretty out of date (so trying to use the lib caused
version conflicts with the version we were already using in our app)

2. Our draftjs content wasn't stored as a string, it was stored as a
map.  Removing json parsing will let the user parse it if they need
to (in whatever way they want), and let those who don't need to use
it out of the box.
buob and others added 28 commits February 15, 2019 12:14
Inline style ranges (right now only `BOLD` and `ITALIC`) and entity
ranges (right now only `LINK`)
Which can be hooked into in custom processors
This made us able to do some unique things, like transforming content
in our custom entities, that we were unable to do with our simpler
approach.
Rewrite inline ranges as a tree
Handle headers four through six in process_block
Because, yes, line length matters 😬
I hope this doesn't bite us in the butt, buttttt... there is a line length
limit and this is really the best place IMO to put the newline because otherwise
it could get converted to a space and be in a bad spot...
buob and others added 3 commits February 13, 2020 11:15
https://trello.com/c/DXA1F6ab

Fixes a bug in Outlook that doesn’t respect an outer span’s styling on an inner a tag.
Add ability to control the order in which styles are applied to entities
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.

4 participants