-
Notifications
You must be signed in to change notification settings - Fork 139
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
Name handlers and move them into a separate file. #14
Comments
.on
from the handler callbacks.
@MattB-GA-Boston Is this still revelant since this lesson is done on a whiteboard and in the browser? |
@J-Weeks Are you still doing the lab where you set event handlers? |
This is still relevant. Let's not do coding in the browser. Get developers used to working within |
@jrhorn424 you mean not using the console in the browser? Not sure I agree. I actually think this is a good place to show we CAN use the brower's console to run code that has an impact on the page. If you feel strongly that this isn't good to show (or isn't good to show here), I'm all ears. |
I disagree, but I can't remember why. |
Showing it as a possible debugging/learning aid makes sense to me. Warning against to heavy reliance is probably also appropriate. Also, don't do it and then ask for help because it's not in the app code. |
defacing.js contains some example jQuery for defacing the Broncos page.
Use
require
to link them.See ga-wdi-boston/planning#5
(Formerly https://github.com/ga-wdi-boston/010/issues/4)
The text was updated successfully, but these errors were encountered: