Closed (fixed)
Project:
Manage display
Version:
3.0.0
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2024 at 07:10 UTC
Updated:
30 Apr 2024 at 08:19 UTC
Jump to comment: Most recent
The module should contain composer.json file.
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
astonvictor commentedCreated a new MR with a composer.json file.
Comment #4
adamps commentedAccording to this page https://www.drupal.org/docs/develop/using-composer/add-a-composerjson-file it is optional. What do you see as the advantages?
Why "minimum-stability": "dev"?
Comment #5
raveen_thakur51 commented@. For prod env, I believe it is "stable" to ensure only stable releases are installed. However, for dev, including development versions can be beneficial for testing new features or bug fixes.
** Adding a composer.json file may bring several advantages like Dependency Management, Version Control & ease of updating.
Comment #6
astonvictor commentedthanks @Raveen Thakur
Comment #7
adamps commentedOn the page I linked to in #4 is says this:
When prompted for Minimum Stability []:, hit enter to use the the default of "stable" stability. This will have no effect on websites where your code is installed, but may affect which versions of dependencies are used when running your project's tests. Stable dependencies during testing is preferred to unstable ones.
I searched all the modules installed on one of my sites. The majority leave it out altogether so perhaps that's best??
Comment #8
astonvictor commentedok, in that case I’ll close the MR
Comment #10
adamps commentedI have very little time now for Drupal, so I will try to leave you as much freedom as possible. You can commit it is you like.
Comment #12
astonvictor commentedthanks.
merged the MR