Hey all,
I've been encouraged to write an update on a 1%* project that I've been working on: separating the HTML formatter and APIs from the Minerva skin.
Right now, I've created a new extension, which contains the code, associated configuration variables, and unit/integration tests [0] and am running it alongside a cut down version of the MobileFrontend extension [1] locally.
My long-term goal is to further separate out the HTML formatter into a versioned library and to version the API extension so that we can make smaller, more easily reasoned about changes to smaller, more easily reasoned about components and update the (relative) titan that is the MobileFrontend extension more responsibly.
My short-term goals are:
* to *cover* the new extension in integration tests so that I can make structural changes * to get the unit tests passing without hitting the DB * to document the new extension thoroughly * to reduce the binding between the two extensions to exactly one call [2] * to get the extension deployed
Cool? Cool!
–Sam
* Not a typo
[0] https://github.com/phuedx/MobileView [1] https://github.com/phuedx/mediawiki-extensions-MobileFrontend [2] https://github.com/phuedx/mediawiki-extensions-MobileFrontend/blob/dd9e99e0f...
Thanks,
Jeff Hobson
On Tue, Sep 1, 2015 at 9:52 AM, Sam Smith samsmith@wikimedia.org wrote:
Hey all,
I've been encouraged to write an update on a 1%* project that I've been working on: separating the HTML formatter and APIs from the Minerva skin.
Right now, I've created a new extension, which contains the code, associated configuration variables, and unit/integration tests [0] and am running it alongside a cut down version of the MobileFrontend extension [1] locally.
My long-term goal is to further separate out the HTML formatter into a versioned library and to version the API extension so that we can make smaller, more easily reasoned about changes to smaller, more easily reasoned about components and update the (relative) titan that is the MobileFrontend extension more responsibly.
My short-term goals are:
- to *cover* the new extension in integration tests so that I can make
structural changes
- to get the unit tests passing without hitting the DB
- to document the new extension thoroughly
- to reduce the binding between the two extensions to exactly one call [2]
- to get the extension deployed
Cool? Cool!
–Sam
- Not a typo
[0] https://github.com/phuedx/MobileView [1] https://github.com/phuedx/mediawiki-extensions-MobileFrontend [2] https://github.com/phuedx/mediawiki-extensions-MobileFrontend/blob/dd9e99e0f...
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Looks interesting!
On Tue, 2015-09-01 at 14:52 +0100, Sam Smith wrote:
Hey all,
I've been encouraged to write an update on a 1%* project that I've been working on: separating the HTML formatter and APIs from the Minerva skin.
Right now, I've created a new extension, which contains the code, associated configuration variables, and unit/integration tests [0] and am running it alongside a cut down version of the MobileFrontend extension [1] locally.
My long-term goal is to further separate out the HTML formatter into a versioned library and to version the API extension so that we can make smaller, more easily reasoned about changes to smaller, more easily reasoned about components and update the (relative) titan that is the MobileFrontend extension more responsibly.
My short-term goals are:
- to *cover* the new extension in integration tests so that I can
make structural changes
- to get the unit tests passing without hitting the DB
- to document the new extension thoroughly
- to reduce the binding between the two extensions to exactly one
call [2]
- to get the extension deployed
Cool? Cool!
–Sam
- Not a typo
[0] https://github.com/phuedx/MobileView [1] https://github.com/phuedx/mediawiki-extensions-MobileFrontend [2] https://github.com/phuedx/mediawiki-extensions -MobileFrontend/blob/dd9e99e0f805812914b8d3266dc17239b2968a24/include s/MobileFrontend.body.php#L38 _______________________________________________ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
A valiant effort, Sam! Would love to hear more about your personal experience tackling a legacy component w/ a TDD approach when all is said and done.
On Wed, Sep 2, 2015 at 6:45 AM, Bahodir Mansurov bmansurov@wikimedia.org wrote:
Looks interesting!
On Tue, 2015-09-01 at 14:52 +0100, Sam Smith wrote:
Hey all,
I've been encouraged to write an update on a 1%* project that I've been working on: separating the HTML formatter and APIs from the Minerva skin.
Right now, I've created a new extension, which contains the code, associated configuration variables, and unit/integration tests [0] and am running it alongside a cut down version of the MobileFrontend extension [1] locally.
My long-term goal is to further separate out the HTML formatter into a versioned library and to version the API extension so that we can make smaller, more easily reasoned about changes to smaller, more easily reasoned about components and update the (relative) titan that is the MobileFrontend extension more responsibly.
My short-term goals are:
- to *cover* the new extension in integration tests so that I can
make structural changes
- to get the unit tests passing without hitting the DB
- to document the new extension thoroughly
- to reduce the binding between the two extensions to exactly one
call [2]
- to get the extension deployed
Cool? Cool!
–Sam
- Not a typo
[0] https://github.com/phuedx/MobileView [1] https://github.com/phuedx/mediawiki-extensions-MobileFrontend [2] https://github.com/phuedx/mediawiki-extensions -MobileFrontend/blob/dd9e99e0f805812914b8d3266dc17239b2968a24/include s/MobileFrontend.body.php#L38 _______________________________________________ Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l
Mobile-l mailing list Mobile-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l