View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017155 | MMW 5 | Extensions framework | public | 2020-12-01 02:23 | 2021-05-26 23:00 |
| Reporter | drakinite | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0.1 | Fixed in Version | 5.0.1 | ||
| Summary | 0017155: info.json parsing does not have a case for invalid JSON | ||||
| Description | When installing an extension, if info.json is syntactically invalid JSON, it will always display the following message: "Invalid Addon! Addon version is not in the form %d.%d.%d." There should be a separate case for invalid JSON. | ||||
| Steps To Reproduce | example of invalid info.json (comma at the end): { "title": "My Extension", "id": "MyExtension", "description": "invalid", "version": "1.0.0", "author": "nobody", "type": "skin", } | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2408 | ||||
|
|
Jordan, are you looking for a message to help addon authors? e.g. Invalid addon! (.json error) Note: Invalid addon! is an existing string so the above could be added without any new translation strings (i.e. since '.json error' is targetted at developers, it doesn't need to be translated). |
|
|
I think that's perfect - though preferably, "Invalid addon! (JSON error)", since JSON is an acronym. Still can be done without translations. |
|
|
Fixed in build 2408. |
|
|
Verified 2408; no regressions found in installing addons. Closing |
