Hrm, that's distressing. Is there any way to differentiate between items that only show up on the API docs vs. ones that also show up in the web UI?
Personally, while it seems convenient and time-saving to reuse the web UI strings for the API docs, if the side-effect is making it harder to update the API docs, then it sort of seems like there is a risk that people will be reticent to improve the documentation for the API calls, lest it risk impacting the web UI.
Anyway, if I can find a way to discern which strings are used by the web UI, I can strip out those changes from this branch.
Hrm, that's distressing. Is there any way to differentiate between items that only show up on the API docs vs. ones that also show up in the web UI?
Personally, while it seems convenient and time-saving to reuse the web UI strings for the API docs, if the side-effect is making it harder to update the API docs, then it sort of seems like there is a risk that people will be reticent to improve the documentation for the API calls, lest it risk impacting the web UI.
Anyway, if I can find a way to discern which strings are used by the web UI, I can strip out those changes from this branch.