View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 18292 | Feature requests | Other | public | 2022-07-28 10:38 | 2026-11-20 14:06 |
| Reporter | DenisChenu | Assigned To | |||
| Priority | none | Severity | @70@ | ||
| Status | acknowledged | Resolution | open | ||
| Summary | 18292: What is included in API : clean list for dev | ||||
| Description | Need a clean list of : What is included or not in API | ||||
| Steps To Reproduce | See : https://bugs.limesurvey.org/view.php?id=18276 we must really write clearly what is in API or not. We have a lot of API broker happen in minor version for Theme or Plugins See https://gitlab.com/SondagesPro/SurveyThemes/skelvanilla/-/commit/014d061aa666ed631d2e4cb79102a1112f328147 Some other example : https://bugs.limesurvey.org/view.php?id=18211 , can broke JS + SurveyTheme updating theme.css etc … I mean : if js workaround are part of API : we can not update any answers html without a API upgrade | ||||
| Tags | No tags attached. | ||||
| Bug heat | 4 | ||||
| Git branch / Pull Request URL | N/A | ||||
|
In Linux land they say, "kernel must not break user space", which I think is a good rule of thumb for minor and patch updates. That is, if any external user or dev depends on a certain HTML or call, it should not be changed, except for major version updates. |
|
|
You mean : if it can be accessible by admin GUI ? All potential 3.X API broker : https://github.com/LimeSurvey/LimeSurvey/commits/3.x-LTS/themes/survey/vanilla Even updating theme file must be forbidden without API upgrade … |
|
No, I mean, if anyone - user or dev - depends on the HTML having a certain structure, it shouldn't be changed unless we bump major version. |
|
Then : we can not update anything without major version bump … etc … |
|
Well, I guess it depends on if someone or something is relying on it, right? :) |
|
Then : wait for a user ask on forum or report the issue? There are a lot … But user never report issue … they just go on another system or hack themself … You can not do it like this : Do it and wait for user say it broke. It's OK for Holch, Tony , etc … but all other user never report such issues |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-07-28 10:38 | DenisChenu | New Issue | |
| 2022-07-28 10:38 | DenisChenu | Steps to Reproduce Updated | |
| 2022-07-28 11:01 | ollehar | Note Added: 71220 | |
| 2022-07-28 11:01 | ollehar | Bug heat | 0 => 2 |
| 2022-07-28 11:01 | ollehar | Note Edited: 71220 | |
| 2022-07-28 11:06 | DenisChenu | Note Added: 71221 | |
| 2022-07-28 11:06 | DenisChenu | Bug heat | 2 => 4 |
| 2022-07-28 11:20 | ollehar | Note Added: 71222 | |
| 2022-07-28 12:15 | DenisChenu | Note Added: 71225 | |
| 2022-07-28 12:17 | ollehar | Note Added: 71226 | |
| 2022-07-28 15:57 | DenisChenu | Note Added: 71230 | |
| 2026-11-19 22:50 | c_schmitz | Status | new => acknowledged |
| 2026-11-20 10:33 | c_schmitz | Category | Documentation => (No Category) |
| 2026-11-20 14:06 | c_schmitz | Project | Bug reports => Feature requests |
| 2026-11-20 14:06 | c_schmitz | Category | (No Category) => Other |