Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Need user interface integration tests that exercise the front end in context
  2. Need complete functional specifications
  3. Need custom forecast block auto-handling code, via optional fields or optional state
  4. Currently using JSON Objects, not PUT and POST Params, for PUTS, POSTS, and DELETES, therefore currently all PUTS, POSTS and DELETES need to have row body JSON parsing.
  5. Because we do not have classical resource/resourceID REST structure, we are using PUTS for create resource and POST for resource update, classical REST would reverse the PUT and the POST (PUT for update, POST for create).