Skip to content

AppDevCourse/omnicalc-debug

 
 

Repository files navigation

Omnicalc Debug

Standard Workflow

  1. Start the web server by running bin/server.
  2. Navigate to your live application preview.
  3. As you work, remember to navigate to /git and commit often as you work.
  4. When you feel confident that your app matches the target, run rails grade. Running rails grade to get feedback is a terrible feedback loop.

Target

Here is your target

The starting point of this app has four different forms which take input from users, some of which run through the Google Maps API and the DarkSky API, be sure to update your enviroment credientals.

YOUR JOB: Debug all 4 forms.

Debugging checklist:

  1. READ the error message. Extract as much useful information from it as possible.
  2. If there's no error message, find another way to give yourself feedback; make the invisible visible.
    • Use the server log.
    • Print things; in this new world, that means use embedded Ruby tags (<%= %>) in the view templates. We can't use the p method anymore since we aren't writing command line programs anymore.
  3. If all else fails — the error message isn't helpful, or there isn't one and you can't spot the issue visually — delete the offending code (or comment it out), and re-type the R→C→A→V from scratch. Hopefully you've been making lots of git commits, so there's no fear in doing so.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • Ruby 86.6%
  • HTML 10.4%
  • Dockerfile 2.0%
  • Other 1.0%