Closed (fixed)
Project:
Version Control API
Version:
6.x-2.x-dev
Component:
API module
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
22 Aug 2010 at 16:57 UTC
Updated:
15 Apr 2014 at 22:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
marvil07 commentedget out that var_dump :-p
Comment #2
marvil07 commentedtagging
Comment #3
chrisstrahl commentedtagging for sprint 2
Comment #4
chrisstrahl commentedComment #5
sdboyer commentedThink I've got this all done locally, will be reintegrating into CVS presently. Also fixing the title, it was actually describing the opposite of what needed to be done.
Comment #6
sdboyer commentedNot so sure about this, actually.
Comment #7
sdboyer commentedActually, it's more helpful to leave this with a separate property name by default. Given that the allowed characters are different for most vcs usernames vs. Drupal usernames, we may as well as use a different variable name for it. So, scratching this.
Comment #8
marvil07 commentedOk, so this is only about consistency.
So we need to revert http://github.com/sdboyer/versioncontrol/commit/189985ef2fc592c15be7700b...
Comment #9
sdboyer commentedOK, wow I COMPLETELY forgot about how this actually was a problem because of the db <-> class property naming mapping. It's not just a convenience thing like I presented last week, this actually needs to be done. So, this is indeed active, but because it needs to be finished up, not reverted.
Comment #10
sdboyer commentedActually, yeah, let's revert that, and change the name of the field in the database. Whew.
Comment #11
sdboyer commentedReverted the changes listed in the original commit. Will post a patch presently with the db changes.
Comment #12
sdboyer commentedSorry, I got a bit distracted with trying to test this change. Ended up hacking on tests, then ended up writing half of that abstracted framework for allowing tests in VCAPI to test backends, per their availability. It's kinda cool, I'll post a patch in another issue soon.
Anyway, the patch is attached here. It seems to basically work well, but another set of eyes would be great - especially until we get the tests definitively fixed.
Comment #13
marvil07 commentedI think it was only one more, but I also change one doc blocks and a variable name to be consistent.
Comment #14
sdboyer commentedCommitted: http://drupal.org/cvs?commit=446862
Comment #15
sdboyer commentedOK, noticed that I missed a couple of fields to change over. And when I fixed them, there were suddenly a lot MORE failures in the versioncontrol_account_status tests...which is weird. Why were they passing before, when this was clearly broken?
marvil07, could you check out the attached patch and look into fixing the tests (and make sure all the necessary changes have been made wrt the original purpose of this issue)?
Comment #16
sdboyer commentedComment #17
marvil07 commentedIt really took me a while to figure out why account status is failing at the test, that was the only automated way I have to actually review this nomenclature change is working. But I end up fixing several stuff at its functionality.
So, I have a patch that make account status test work! (aka all test passing!)
@sdboyer: I would like to commit this after your review.
Comment #18
marvil07 commentedtagging
Comment #19
cweagansThis looks good. I'd say it's okay to be committed.
Comment #20
marvil07 commentedI just committed the last patch, feel free to re-open this if necessary.
\o/ patches working 100%