Closed bubaflub closed 7 years ago
Probably related to #46, as it would require the same refinement on checking table-type globals. Here, setting a specific (member) field obviously is okay, while other assignments might be undesired.
It's not fine-grained enough but for now as a temporary fix I'll remove remove read-only status of ngx
global in ngx_lua
std.
When running against our lua-nginx codebase I have to add
ignore = {"122/ngx"}
to .luacheckrc since luacheck flags a number of valid lua-nginx calls as wrong.Simple example:
But according to https://github.com/openresty/lua-nginx-module#ngxstatus this is completely valid lua-nginx code. It seems like having
ngx
as a read-only global isn't fine-grained enough or not quite accurate.