fix: correct spelling mistake in API, doc and tests (#5934)

[PinkMoustacheMan]

• mark misspelled method as deprecated
• add new method with correct spelling
• correct spelling of method in docs and test classes

[monperrus]

thanks for the PR. would you have a look at the failing CI job?

[SirYwell]

Should the method added to the interface be default and delegate to the deprecated method to avoid breaking changes?

[PinkMoustacheMan]

Should the method added to the interface be default and delegate to the deprecated method to avoid breaking changes?

I believe it should be the other way around.
The newly added method is the "correct" one. If its implementation changes (let's just assume the changing implementation is backwards compatible) then the deprecated method should follow suit.
The "incorrect" method should not be the one that is actively being maintained.

[monperrus]

Per the theory of software engineering, there should be no delegation:

• the deprecated method is frozen, kept as is for backward compatibility, and will be removed in the future after the deprecation period (do we have an official one in Spoon?)
• the new method is the one actively maintained.

Here, the code is so simple, so I'm happy to merge anyway when CI is green.

[PinkMoustacheMan]

I do agree with the notion that deprecated methods should not change anymore, so I reverted that change.
I also fixed the whitespace issue, I thought this was not part of the checks (or that it would be fixed as part of a commit hook or CI step).

[monperrus]

Thanks.

Why do we have a public and a private version of the same method AFAIU? see private boolean shouldBeProcessed

[PinkMoustacheMan]

There is a public shouldBeConsumed method as well as a private shouldBeProcessed method.
They are doing the same thing but referencing different fields.

[monperrus]

thanks a lot @PinkMoustacheMan