Ignore non-critical schema errors?

[mal-tee]

Hi,

is it possible to install or update requirements from a composer.json even if unrelated parts of the JSON schema aren't valid?

For example, running update or install with a package like this fails:

{
    "name"      : "test/Test",
    "version"   : "1.0.0",
    "require"   : {}
}

as the name contains uppercase chars.

Is there a way to disable composer's schema validation? I am only interested in automating the installation of potential requirements of random source code, and the require part of the schema seems to be valid.

[Seldaek]

There is no way to do this, and I'm not too keen on allowing it as really the schema should be respected otherwise it leads to other problems down the line.

[mal-tee]

Thank you for the answer. That's a completely reasonable approach. :D

In the mean time I've resorted to falling back to composer 2, if 3 fails to verify a given composer.json.

[Seldaek]

I'm guessing you mean Composer 1 if 2 fails ;)

[mal-tee]

Oops. Yes :'D