ucdavis / ucdavis/ipa-client-angular
SchedulingView: undefined is not an object (evaluating 'term.code')
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
URL: https://ipa.ucdavis.edu/scheduling/31/2018/9 User: Thielen, Christopher Kerberos: cthielen Full Error: undefined is not an object (evaluating 'term.code') Stack: https://ipa.ucdavis.edu/js/schedulingApp.js?rel=1511979802334:6:9214 processQueue@https://ipa.ucdavis.edu/js/lib.js:14:6274 https://ipa.ucdavis.edu/js/lib.js:14:6551 $digest@https://ipa.ucdavis.edu/js/lib.js:14:17640 $apply@https://ipa.ucdavis.edu/js/lib.js:14:20379 https://ipa.ucdavis.edu/js/lib.js:14:13040 completeOutstandingRequest@https://ipa.ucdavis.edu/js/lib.js:11:8152 https://ipa.ucdavis.edu/js/lib.js:11:11299
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the scheduling URL and inspect schedulingApp.js at the reported stack location, then trace the preceding term lookup before term.code is accessed. Use the available error details to identify why term is missing and verify that the page no longer throws this exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100