Problem/Motivation

./composer.json is valid, but with a few warnings
See https://getcomposer.org/doc/04-schema.md for details on the schema
No license specified, it is recommended to do so. For closed-source software you may use "proprietary" as license.

Steps to reproduce

Run composer validate

Proposed resolution

Use License

CommentFileSizeAuthor
#3 after.png4.82 KBlarisse
#3 before.png43.04 KBlarisse
#2 3198752-2.patch1015 bytesvipin.mittal18

Comments

vipin.mittal18 created an issue. See original summary.

vipin.mittal18’s picture

vipin.mittal18
He/Him
Primary language English
Location Greater Noida, India
commented
Status: Needs work » Needs review
StatusFileSize
new 3198752-2.patch1015 bytes

Kindly apply the attached patch to resolve the composer.json license warning.

larisse’s picture

larisse commented
Assigned: vipin.mittal18 » Unassigned
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new before.png43.04 KB
new after.png4.82 KB

Hi!
The patch #2 remove the warnings, solving composer.json license warnings.

rsvelko’s picture

rsvelko commented
Assigned: Unassigned » rsvelko

Done. Committed. If you're using the -dev version of the module or a git clone - the fixed composer.json is available to you.
Those using official releases - should wait for the new versions / releases.

rsvelko’s picture

rsvelko commented
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.