Draft-js: ContentState.js still uses DraftEntity internally in 0.11.0-beta

[Leandowich]

Do you want to request a feature or report a bug?
Missing feature

What is the current behavior?
src\model\immutable\ContentState.js still uses the old DraftEntity internally in version 0.11.0-beta

(Don't worry about the linting warnings in the image)

This is most likely related to #2038

What is the expected behavior?
That an immutable OrderedMap is used, similar to the implementation in the stale branch v0.11.0-alpha

Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
0.11.0-beta, chrome version 73.0.3683.75 (64 bit)

[claudiopro]

Thanks for reporting this issue @Leandowich, I'll follow up on this. @flarnie, @niveditc can you shed some light on this?

[claudiopro]

@Leandowich just following up, I haven't gathered enough context on this change and would love to hear from previous contributors about the intent and scope of this API change.

All in all, in the interest of getting releases flowing again, we can't commit to addressing this for v0.11.0. It will have to wait a bit more. Thanks for understanding!

[Leandowich]

Thank you @claudiopro, it is awesome to see that the project is active again. I would like to point your attention to the roadmap here: https://github.com/facebook/draft-js/blob/master/meta/roadmaps/2017-h1.md

The primary feature of the envisioned v0.11.0 is to deprecate the DraftEntity that is used in the internals (ContentState) of draft-js as an entity map. The idea was to replace this with an immutable-js OrderedMap to be more inline with the rest of the draft-js implementation (as far as I have understood from reading the roadmap and meeting notes). The current project I am working on also has issues since the current implementation using the DraftEntity is not used correctly if the state is created using createFromBlockArray.

It is perfectly understandable that you need to gather additional context, but if the current implementation could at least be brought inline with the old DraftEntity until then, that would be great!

Thank you for your attention to this issue

[claudiopro]

The roadmap published by @flarnie in 2017 was pretty ambitious, however in the interest of resuming releases and given the current (little) bandwidth of new maintainers we may have to significantly downsize expectations.

Our priority is to get to a consistent working state without significant performance or functionality regressions, and resume addressing issues found internally and within the community with a constant stream of minor releases.

Hope this helps understand how we prioritize issues.

[cdow]

Would there be any interest in a PR that replaces DraftEntity?