Module installs a large set of dependencies undocumented on project page

Created on 9 February 2024, 10 months ago
Updated 19 March 2024, 9 months ago

Problem/Motivation

To build trust on a user base I recommend to better document the reasons for such a list of dependencies on a "sub" module to layout builder. There are 7 dependencies where not all are self explanatory and which should be mentioned on the project page explaining what they are used for.

Example: Why does this layout module needs logging capacities with monolog? Or why does it need http authentication with intervention/httpauth?

Steps to reproduce

Install module as usual with composer and watch the command line output while installing.

Proposed resolution

Document the reasons for this dependencies and what they do in short notes.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Closed: outdated

Version

1.0

Component

Code

Created by

🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024