[COMPASS-2613] Handle throwing errors in code generation Created: 07/Mar/18 Updated: 17/Apr/18 Resolved: 17/Apr/18 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Export to Language |
| Affects Version/s: | None |
| Fix Version/s: | 1.15.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Anna Herlihy (Inactive) | Assignee: | Alena Khineika |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | COMPASS-2309 | ||||||||
| Sprint: | Compass Sprint Nipsey Hu$$le, Sprint Ol' Dirty Bastard, Sprint Phife Dawg | ||||||||
| Description |
|
We should throw our own errors that give the most helpful message possible. (Not the same as providing semantic checking for the input code. This ticket is just to define the error class so we can throw errors if the tree is malformed, the types don't match, etc. There will be a separate ticket, that depends on this one, for going through and type checking or limiting input to making JSON objects). |