Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure these functions don't bleed into the global scope #70

Merged
merged 4 commits into from May 18, 2012

Conversation

tswicegood
Copy link
Contributor

This makes sure that all of these functions are assigned to variables
assigned to the current scope, rather than the global scope. It also adds a
trailing semi-colon to make sure various linters are happy.

This makes sure that all of these functions are assigned to variables
assigned to the current scope, rather than the global scope.  It also
adds a trailing semi-colon to make sure various linters are happy.
@adrianholovaty
Copy link
Member

Thanks for this cleanup, @tswicegood!

adrianholovaty added a commit that referenced this pull request May 18, 2012
Cleaned up various JavaScript in admin JS.
@adrianholovaty adrianholovaty merged commit 4b75546 into django:master May 18, 2012
@jezdez
Copy link
Contributor

jezdez commented May 20, 2012

Hm, seems like there was a ticket open, too. Please for the love of god, mention ticket numbers when creating pull requests.

@tswicegood
Copy link
Contributor Author

Doh! Didn't see the issue when I searched. :-/

@tswicegood
Copy link
Contributor Author

Oh wait -- was it the ticket I opened? I did the reverse reference from it to here I thought...? My workflow is generally create the PR first, then the ticket in Trac as housekeeping assuming it looks good to other people.

I'll try to make sure to update the description on PRs once a ticket is open though.

@jezdez
Copy link
Contributor

jezdez commented May 21, 2012

Right, the problem occurs when a pull request is merged without knowing there is a ticket. The green button is rather tempting ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants