Document how to add a new development dependency for an extension in Quibble
Closed, DuplicatePublic0 Estimated Story Points
Actions

Assigned To

None

Authored By

	greg
	Jul 12 2019, 6:32 PM

Description

11:26:09 <ejegg> what's the quibble-compatible way to add a dev dependency for a mediawiki extension?
11:26:22 <ejegg> I just tried adding a dev dependency for DonationInterface
11:26:46 <ejegg> and the quibble test is failing: https://gerrit.wikimedia.org/r/522525
11:27:52 <ejegg> when I try to use a class included in a library added to the composer.json require-dev section
11:29:38 <ejegg> Ah, I guess we should set merge-dev to true in our core branch composer.json merge-plugin node?

https://doc.wikimedia.org/quibble/

Related Objects

Mentioned Here: T220723: Install extension require-dev dependencies in wmf-quibble-vendor-mysql-hhvm-docker

Event Timeline

greg triaged this task as Medium priority.Jul 12 2019, 6:32 PM

greg created this task.

greg moved this task from INBOX to Ready on the Release-Engineering-Team-TODO (201907) board.

<legoktm> ejegg: so...the answer is you add it as a mw core dev dependency :(

Not sure if this is something to document in the quibble docs or not....

Erik Bernhardson has hit the same issue to add symfony/yaml for the CirrusSearch extension. T220723

hashar closed this task as a duplicate of T220723: Install extension require-dev dependencies in wmf-quibble-vendor-mysql-hhvm-docker.Jul 17 2019, 7:09 AM

Document how to add a new development dependency for an extension in QuibbleClosed, DuplicatePublic0 Estimated Story PointsActions

Description

Related Objects

Event Timeline

Document how to add a new development dependency for an extension in Quibble
Closed, DuplicatePublic0 Estimated Story Points
Actions