Support for PLAIN BB-Code and CODE=rich

[asccc]

Fixes #29
Fixes #30
Fixes #32
Fixes #37

I also added phpunit and wrote some tests as mentioned in #31
We can add phpunit to our phan action, too.

[jr-cologne]

Yep, adding phpunit to our GitHub actions would be cool.

Thank you for fixing/addressing these bugs/issues as well as your additional improvements of the code in general.

I have already provided some feedback, even though you are probably still working on it.
I will go ahead and fix your mistakes in the comments and extract the helper methods for the tests into a trait.

[asccc]

I had to remove the parser-trait, because currently there is no autoloader in place to load classes inside the tests-folder.

[asccc]

Argh, i missed the change in composer.json ... autoloading in tests/ was possible ☹️

[jr-cologne]

Yep, I actually set everything up for phpunit.

[asccc]

I think we're good to go now 😃

[asccc]

I decided to implement CODE=rich (as mentioned in #37) in this pr, too, because this requires another rewrite of the parser.
It wouldn't make sense to merge this right now.

[jr-cologne]

Alright, take your time. All looks very good to me. 😃

[asccc]

Should work now 😃

[asccc]

Somehow my latest push is not showing up here?

[asccc]

Well, anyway @jr-cologne i'm not 100% satisfied with the api. What do you think?
You can see the latest changes in my fork: asccc@40c2803

[jr-cologne]

Sorry, I have kinda lost track of the changes you have applied here. 😄
I will try to get an overview over your code as well as the API in general in order to answer your question.
Just give me a moment to take a closer look at it.

[jr-cologne]

Ok, to me, the API and such looks perfectly fine.
What do you exactly not like yet?

Skipping the formatter if the language is "text" would probably speed things up a little bit as the formatter wouldn't have to go through all potential formatters to finally find anything which formats plain text. So feel free to make this change.

[asccc]

I absolutely don't like the fact that ElemNode's body can be a NodeList or simply a string.
This requires assertions all over the place and makes the tests type unsafe:

(All the red highlights are failed type-checks).

[asccc]

"Besser wirds erstmal nicht" i guess 😆

[jr-cologne]

Oops, I accidentally pushed something. I hope I've not broken anything. 😅
Looks like to merged your parser branch...

[jr-cologne]

Ok, besides one error I get when formatting with prettier, everything looks pretty good. 👍

Here's the output:

Fatal error: Uncaught DevCommunityDE\CodeFormatter\Exceptions\Exception: code formatting failed! stderr: Error: EACCES: permission denied, mkdir '/var/www/.npm' command not found: prettier

Test input:

Hallo
[CODE=css].test { padding: 10px; }[/CODE]
test

This might just be an issue on my end, btw.
If it works for you, feel free to merge.

Before you merge and I forget it: Thank you so much for this huge amount of work you put into this PR! 🥇 🥳 🙌