openresty / openresty/lua-nginx-module
[Feature Request] We do need an approach to disable _G write guard warning
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.8k
- Forks
- 2.1k
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 6
Description
There're times we use some lagacy code, like some libraries, which write directly to global name space.
We do also prefer it to not use global variable, but simply find it troublesome when we have to either quit using existing lib or modify the lib source by hand.
For some reason rawset(_G, 'yaml', false) trick does not always work, we need an official support to disable the warning.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the implementation of the _G write guard warning and the handling of rawset(_G, 'yaml', false). Determine how an official way to disable the warning should be exposed without modifying legacy libraries. Done means the supported option reliably suppresses the warning when requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100