[19:11:18] <James_F>	 Is there a nice way to do conditional (config-based) registration of (action) API modules?
[19:12:17] <James_F>	 I can just return a 'warning' if users try to call it on wikis that it won't work on, but that feels very ugly.
[19:57:46] <Reedy>	 I think you're either adding or removing it in extension functions (or maybe callback) based on a $wg
[20:03:23] <James_F>	 Reedy: That sounds horrendous.
[20:05:09] <Reedy>	 We don't have good conditional registration ways for many things
[20:05:14] <James_F>	 Yeah.
[20:05:16] <James_F>	 Oh well.
[22:39:28] <tgr|away>	 James_F: there is ApiDisabled / ApiQueryDisabled
[22:39:52] <tgr|away>	 but yeah you'll have to do that in a hook
[22:41:14] <tgr|away>	 or you can just remove them completely in a hook. Whichever you think will be less confusing to the user.
[22:41:53] <tgr|away>	 alternatively, you can technically leave them enabled but prevent access via ApiCheckCanExecuteHook. But then it will show up in ApiSandbox etc. so that's probably the most confusing approach.
[22:44:33] <tgr|away>	 (I don't think we have any feature where we support conditional registration in a declarative way. Optional services in ObjectFactory is the only even remotely similar thing I can think of.)