Closed (fixed)
Project:
Gigya - Social Infrastructure
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
17 Mar 2010 at 00:21 UTC
Updated:
5 Aug 2010 at 19:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
EvanDonovan commentedThis will include #688478: Documentation for permissions?.
Comment #2
EvanDonovan commentedUnassigning myself from this. Have added to the roadmap.
Comment #3
azinck commentedMy plan at this point is to knock out the critical bugs/features first and refactor as I go. As I come to features that may require more significant architecture changes we'll assess them at that time. Cleaning up the javascript, however, really is a project unto itself.
Comment #4
EvanDonovan commentedThat makes sense. Did you see the update I just made to the roadmap issue? I'd be curious for your input.
Maybe we should just reduce the scope of *this* issue to code style then (i.e., Coder module). If the module's code style were cleaned up now, that would definitely help us moving forward.
Comment #5
EvanDonovan commentedAside from code style, all the commented out parts of the module that are no longer in use should also be removed. That would just make things simpler for everyone, I think.
Comment #6
add1sun commentedOK, here is a mega patch that hits a lot of the styling/standards cleanup. There are a few important notes here though:
1. I changed a number of PHP function names that were using camelCase. I'm pretty sure I cleaned up all of the internal references but if anyone wrote custom code using those functions, their work will break. We should probably add a note to the README or create an UPDATE.txt for tracking the changes in the module where we can flag this for people. If this seems too extreme I can back those changes out and save it for a V3 of the module, but it really would be good to clean this up. (Should also note that the JS files need a similar cleanup in the other direction, but I'll look at that when I get to them.)
2. The OAuth.inc and all JS files have not been done yet, aside from a global white space cleanup I did.
3. I left a lot if "Undocumented XXX" in the comments, which I'll go back and fill in over time, but I wanted to set up the expected standard in case anyone else feels like helping out with that. ;-)
Comment #7
azinck commentedThanks, add1sun. I've reviewed your changes and committed to dev.
Comment #8
azinck commentedComment #9
EvanDonovan commentedThanks, so much, add1sun for doing this. I am probably going to test the Gigya dev release tomorrow, since I realized a way that I can use it on my site while still using panel pages (that disable regions).
Comment #10
add1sun commentedHere is a follow up patch that fixes up the JS standards a bit, fixes a few camel/underscore things I missed, cleans up some more formatting stuff, along with a few WTF? comments. ;-)
Comment #11
azinck commentedThanks,
Unfortunately I committed a minor change (variable naming problem) after checking in your last patch so this patch is not rolled against the latest version of dev. I'm not going to have time to mess with it right now so if it's important to you that it get checked in before Sunday then I'd love it if you'd re-roll. Otherwise I'll take care of it later. Thanks again!
Comment #12
azinck commentedNever mind :) -- found the time. It's now committed. I made another small change so you'll want to update to the latest dev before rolling any more patches. I'll also start documenting some of the functions as I go.
Comment #13
add1sun commentedWoot! Here is another one. We were spitting a ton of PHP notices, which pointed out some oopsies. The biggest line change was moving the constants into the .module file instead of admin.inc because you are using those constants in more than one file now. I also removed the module version constant (and the 2 places it was used, one of which wasn't actually called anywhere) since we'd need to keep remembering to update it manually which is silly. People can see which version they are using in the module admin page.
Comment #14
azinck commentedI'm sure glad I haven't done much coding on this lately, merging would be annoying ;). J/k, in all seriousness, thanks for the patch.
Comment #15
add1sun commentedANy chance we can get this last patch in soon so we don't end up with funky conflicts? I think we can call this closed after this one and any additional cleanups down the road should be in new issues.
Comment #16
azinck commentedOk, finally got around to committing to dev! Thanks!
Comment #17
EvanDonovan commented@add1sun: Were the permissions that weren't being used by the module removed? That was a cleanup someone had asked me about a while back.