lot of bugs about react-lite

[himalayafan]

I was playing around a little more, so I have to add this:

• TypeError: parentElement.appendChild is not a function
• Uncaught TypeError: Cannot read property 'replace' of undefined

[himalayafan]

TypeError: Cannot read property 'tagName' of null

[Lucifier129]

Can you add some simple demos here?

[himalayafan]

I will soon.

I got some good news for you. I talked to a friend of mine. He is an expert on this and are willing to help you out. A lot of work to do he told me, but I saw his new mount code.
If you want his help, is there a place you can chat with him?

[Lucifier129]

That's great, We can talk about react-lite at https://gitter.im/Lucifier129/react-lite

[himalayafan]

I will notify him. He is occupied just now finishing a demo code, but will be there shortly.

[himalayafan]

@Lucifier129 He contacted you, but you wasn't there.

[Lucifier129]

sorry about that, I am talking with him now.

[himalayafan]

@Lucifier129 I understand that you two want to do different things.

Anyway. DId you notice what he just pushed - simple mount method? It does everything and seem to solve some of the issues I found in react lite.

It also have an option for diffing children very smart.

[Lucifier129]

I stared his project, will focus his work : )

[himalayafan]

@Lucifier129 He told me now that he wrote to you on chat, and he also solved several issues you faced with react lite. Is there anything there you can use for react lite?

[Lucifier129]

I got it.

Since that is not about the subject of this issue, let's focus the bugs you said.

Can you add some demos to show the problems?

[himalayafan]

Hi. Most of this seems to be fixed in dev branch. However. Sometimes when I update from a element node, to a text node. I get this warnings, or I get undefined instead of the node get removed.
If I then again try to re-patch the node that should have been removed, but have undefined as text, I get this errors.

So most of this errors are related to various combos I did when I do update.

[Lucifier129]

close this issue and will reopen if new error appears with a simple demo to show what happen, or create a new issue instead.