Opened 11 years ago
Last modified 3 years ago
#2380 new defect
Better error messages for API calls
| Reported by: | Per Östlund | Owned by: | somebody |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Interactive Environment | Version: | trunk |
| Keywords: | Cc: |
Description
If an API call is used with invalid arguments:
loadFile(invalid); getErrorString();
then you get this error message:
Error: Class loadFile not found in scope <global scope> (looking for a function or record).
The error message should instead say something about invalid arguments or something, saying that the API call could not be found is very confusing for users.
Change History (15)
comment:1 by , 11 years ago
| Milestone: | 1.9.0 → 1.9.1 |
|---|
comment:2 by , 10 years ago
| Milestone: | 1.9.1 → 1.9.2 |
|---|
This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).
comment:3 by , 10 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:8 by , 8 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:9 by , 7 years ago
| Milestone: | 1.12.0 → Future |
|---|
The milestone of this ticket has been reassigned to "Future".
If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.
If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".
In both cases, a short informative comment would be welcome.
comment:10 by , 7 years ago
| Milestone: | Future → 1.13.0 |
|---|
Replying to perost:
If an API call is used with invalid arguments:
loadFile(invalid); getErrorString();then you get this error message:
Error: Class loadFile not found in scope <global scope> (looking for a function or record).The error message should instead say something about invalid arguments or something, saying that the API call could not be found is very confusing for users.
I totally agree with @perost. Can this be fixed easily?
comment:12 by , 5 years ago
| Milestone: | 1.14.0 → 1.16.0 |
|---|
Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0
comment:14 by , 4 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
Postponed until 1.9.1