You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VisualEditor and ActionParse are really both the same api, just with different parameters, and are both normally used when the target is mediawiki in my experience.
So my question is, can I use --forceRender to cause the RestApi to be used and if so what value should I use? The obvious answer would be RestApi (or restapi as the others are all lowercase), but I didn't find this in the code and when I tried it I still got the action api.
The text was updated successfully, but these errors were encountered:
True, and restapi is not among them, which I took to be an error. So if the --help is accurate and there is no value of --forcerender to cause mwoffliner use restapi, under what circumstances does mwoffliner use the restapi and is there any way to force it to do so?
https://github.com/openzim/mwoffliner/wiki/API-end%E2%80%90points lists 5 endpoints, 3 for mediawiki including VisualEditor and ActionParse currently implemented, and RestApi, which I believe is new to the current dev version.
VisualEditor and ActionParse are really both the same api, just with different parameters, and are both normally used when the target is mediawiki in my experience.
https://github.com/openzim/mwoffliner/wiki/Frequently-Asked-Questions mentions the runtime parameter --forceRender as a means of choosing an api. This parameter is also described in https://github.com/openzim/mwoffliner/blob/main/src/parameterList.ts, which gives 3 values allowed: VisualEditor, WikimediaDesktop, and WikimediaMobile. (This file supplies the help for mwoffliner I believe.)
So my question is, can I use --forceRender to cause the RestApi to be used and if so what value should I use? The obvious answer would be RestApi (or restapi as the others are all lowercase), but I didn't find this in the code and when I tried it I still got the action api.
The text was updated successfully, but these errors were encountered: