Allow pass null argument to methods Tag::class(), Tag::replaceClass(), BooleanInputTag::label() and BooleanInputTag::sideLabel()

[vjik]

Q	A
Is bugfix?	❌
New feature?	✔️
Breaks BC?	❌
Fixed issues	-

Also update dev dependencies and fix psalm errors

[terabytesoftw]

Null does not solve the problem, you can still pass an empty string, and if the method is a string, why complicate it, in addition to not being consistent for example:

Example 1:

CustomTag::name('span)->attributes(['class' => 'tests 1')->class('')->render();

expected:

<span class="test 1"></span>

output:

<span class="test 1 "></span>

Example: 2

CustomTag::name('span)->class('')->render();

Expected:

<span></span>

output:

<span class=""></span>

[vjik]

First case is valid:

// Should be <span class="test 1"></span>
CustomTag::name('span)->attributes(['class' => 'tests 1')->class('')->render();

Second case is not valid. I think code CustomTag::name('span')->class('')->render(); should be result <span class=""></span>.

[terabytesoftw]

Second case is not valid. I think code CustomTag::name('span')->class('')->render(); should be result <span class=""></span>.

What is the point of adding class="" for HTML does not have any meaning makes it <tag class></tag>

[samdark]

Agree with @terabytesoftw in this case.

[samdark]

Discussed once again. It makes sense for consistency sake.

[samdark]

Note that this breaks the interface, so needs major release.

[vjik]

BC saved. We add nullable type in final methods of abstract classes. I'm created issue Roave/BackwardCompatibilityCheck#313