Not sure I understand the NestedUtils.toggleBlocktype

[SamyPesse]

What is the goal of NestedUtils.toggleBlocktype compared to RichUtils.toggleBlocktype ?

I've tried it integrate it into a test application but it doesn't change the block type (editorState stays the same).

[mitermayer]

At the moment, we did not want to duplicate integrations from toggleBlock, so toggleBlock on nested utils levarage from default behaviour of richUtilsToggleBlock, example

clicking toggle on to move from UL to OL converts
UL > LI > H1
to
OL > LI > unstyled
RichUtils.toggleBlock will then
OL > LI > H1

but place cursor selection on the 'unstyped' and uses the blockType 'header-one' to be passed back to the rich utils so that it toggle it back to 'header-one'

This sort of behaviour is a bit of temporary measure so that we don't duplicate code. Maybe nested utils should extend richUtils to avoid this sort of things

[mitermayer]

If nested Utils can't handle the block it will return the same editorState, since its meant to be passed to richUtils toggle block

[mitermayer]

I think maybe we should make nestedUtils extend the richUtils and not expect user to use both at the same time.