Mon, 12 Oct 2020 18:16:18 +0200 mod_http_errors: Dark theme!
Kim Alvefur <zash@zash.se> [Mon, 12 Oct 2020 18:16:18 +0200] rev 11158
mod_http_errors: Dark theme!
Mon, 12 Oct 2020 18:13:20 +0200 mod_http_errors: Use a class on extra data section
Kim Alvefur <zash@zash.se> [Mon, 12 Oct 2020 18:13:20 +0200] rev 11157
mod_http_errors: Use a class on extra data section This CSS selector makes it awkward to add more items.
Sun, 11 Oct 2020 20:25:32 +0100 util.startup: Handle missing nparams field from debug info (not present in 5.1)
Matthew Wild <mwild1@gmail.com> [Sun, 11 Oct 2020 20:25:32 +0100] rev 11156
util.startup: Handle missing nparams field from debug info (not present in 5.1)
Sun, 11 Oct 2020 14:27:28 +0200 core.modulemanager: Fix error if installer path missing
Kim Alvefur <zash@zash.se> [Sun, 11 Oct 2020 14:27:28 +0200] rev 11155
core.modulemanager: Fix error if installer path missing Happens if run outside prosody. Noticed because because the storage tests fail.
Fri, 09 Oct 2020 17:41:10 +0200 util.startup: Include arguments in function string representation
Kim Alvefur <zash@zash.se> [Fri, 09 Oct 2020 17:41:10 +0200] rev 11154
util.startup: Include arguments in function string representation Improves usability of the console when digging around the internals. No specific rationale for the function<file:line>(args) format, it looked best of the variants I tried.
Fri, 09 Oct 2020 17:34:04 +0200 util.startup: Retrieve less data for function string representation
Kim Alvefur <zash@zash.se> [Fri, 09 Oct 2020 17:34:04 +0200] rev 11153
util.startup: Retrieve less data for function string representation debug.getinfo(f) collects more info than what is needed here.
Fri, 09 Oct 2020 16:37:15 +0200 core.moduleapi: Return resource path from module:get_directory() (API BC)
Kim Alvefur <zash@zash.se> [Fri, 09 Oct 2020 16:37:15 +0200] rev 11152
core.moduleapi: Return resource path from module:get_directory() (API BC) :get_directory has so far returned the base directory of the current module source code. This has worked well so far to load resources which tend to be included in the same directory, but with the plugin installer using LuaRocks, extra resources (e.g. templates and other assets) these are saved in a completely different directory. In be73df6765b9 core.modulemanager gained some code for finding that directory and saving it in module.resource_path but now the question is how this should be reflected in the API. A survey of community modules suggest the vast majority use the :get_directory method for locating templates and other assets, rather than the code (which would use module:require instead). Therefore this commit changes :get_directory to return the resource_path when available. This should work for most modules.
Wed, 07 Oct 2020 22:54:12 +0200 core.modulemanager: Add compat for LuaRocks 2.x
Kim Alvefur <zash@zash.se> [Wed, 07 Oct 2020 22:54:12 +0200] rev 11151
core.modulemanager: Add compat for LuaRocks 2.x
Wed, 07 Oct 2020 16:10:51 +0200 core.moduleapi: Use resource path for :load_resource()
Kim Alvefur <zash@zash.se> [Wed, 07 Oct 2020 16:10:51 +0200] rev 11150
core.moduleapi: Use resource path for :load_resource()
Wed, 07 Oct 2020 15:51:37 +0200 core.modulemanager: Locate resources of LuaRocks-installed modules
Kim Alvefur <zash@zash.se> [Wed, 07 Oct 2020 15:51:37 +0200] rev 11149
core.modulemanager: Locate resources of LuaRocks-installed modules Extra non-code files included with a `copy_directories` directive in a LuaRocks manifest will be copied into a per-module and per-version directory under /lib/luarocks/ and all this is there to dig that out so it can be used in e.g. moduleapi :load_resource().
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 tip