Improved ComponentSerializer

[ItsLaivy]

• Enhanced ComponentSerializer#toString methods
• Code enhanced

Now the ComponentSerializer#toString follows the default Minecraft's component json format. Multiples BaseComponents will be now serialized as a json array.

[md-5]

Formatting...

[ItsLaivy]

What does this exactly means?

[md-5]

Look at the diff and build errors please

[ItsLaivy]

Hahah i'm sorry, first time using this. This new commit should fix the tests now.

[ItsLaivy]

I need to do something more? It says the merging is blocked

[Janmm14]

Its only about commit signing - md-5 will resolve that by signing the commit himself, nothing you need to do

[md-5]

Where do you get the default as this?

Won't this break anyone (incorrectly) relying on just accessing [0]?

Re #3490
I think a lot of MC actually can't handle arrays now

[ItsLaivy]

What you mean exactly?

[md-5]

Why do we want arrays?

[2008Choco]

I don't think we do want arrays, but I think this PR is necessary for the sake of consistency between toString() and #parse(). BC already has arrays so it's not really an option to remove them, and while we want to discourage their use I do still find it appropriate to at least improve the way arrays are handled currently :)

Won't this break anyone (incorrectly) relying on just accessing [0]

Yes. Including Spigot. Though I will be moving away from this.

[ItsLaivy]

Why do we want arrays?

If you mean about this:

Multiples BaseComponents will be now serialized as a json array.

I think it's better than the extras. It's a bit buggy, with the arrays we can easily edit the base components using the Gson parser, we will not need to access the extras, and the extras of the extras. I heavily recommend using this new way.

[Janmm14]

redundant