docs: add example composer.json for required cache adapters

[boesing]

Q	A
Documentation	yes

Description

With this example, it is possible to only require those adapters which are required by the project.

[froschdesign]

@boesing
Sorry for the late response!

These are migration notes, right? I would suggest to create a page in the documentation and add this information there. Additionally, a link to the migration page should be added in the readme file.

[boesing]

@froschdesign No, this is just an information on how to configure a current 2.10 based project to not install all unnecessary cache adapters pre-3.0.
I dont think we can provide PHP 8 support to all adapters as most of them are already not supported on PHP 7 either.

So, we dont have to migrate all adapters to PHP 8 at once and let people decide on which adapters they use and to provide PRs only for these adapters.

So in the end, it is forward compatibility to 3.0 aswell as PHP 8 not having to be supported on every adapter for 2.10+.
Thats the idea behind this example.

[froschdesign]

No, this is just an information on how to configure a current 2.10 based project to not install all unnecessary cache adapters pre-3.0.

Then the description with the example should be added to the installation page.

[boesing]

@froschdesign Just to be sure I understand this correct, we dont want to provide informations in README.md but via docs only?

I've also seen that this package is not using the installation template other packages are using. So yes, I can extend the installation page here, but how to achieve that in packages which are using the installation template?
Shouldn't we use the template in each package?

[froschdesign]

@boesing

Just to be sure I understand this correct, we dont want to provide informations in README.md but via docs only?

Oh no. In the optimum case we should provide the same informations (like intro, installation, etc.) in the readme file (here on GitHub and after the installation in the vendor directory) and in the documentation, without duplicating the content. Because duplicating always leads to forgotten updates on one side.
So far, we don't have a (good) solution for this, so it reduces to some text and links.

Shouldn't we use the template in each package?

Yes. I would provide a solution that allows custom content to be added, like the Composer configuration.

[froschdesign]

Some small changes are needed:

• For headline we uses the "Chicago Manual of Style Capitalization Rules"
• MD022 - Headings should be surrounded by blank lines

[boesing]

Bummer! I sweared to myself that I will keep an eye on these chicago headlines 😂

[froschdesign]

🚢