Documentation URL
Description
The Lynx guide contains several signs that its usage section was copied from a different platform and is not self-consistent:
- Both locale versions say the following
js, ttml, and ttss instructions explain using VChart in a Feishu widget, even though this is the Lynx guide.
- The English complete
index.js example retains Chinese-only comments throughout lines 146-156 and later event handling.
- The final English troubleshooting note writes the configuration key as
resolve.enable INodeCache; the Chinese page uses resolve.enableINodeCache.
Expected: clarify whether the TTML/TTSS/Card example is really the supported Lynx integration. If it is, name the correct Lynx environment and translate the remaining English comments; if it is not, replace it with a verified Lynx example. Correct the option token to the actual configuration key.
I fetched all 4,627 open/closed issues and pull requests and found no matches for enable INodeCache or the Feishu-widget wording in a Lynx report. I also compared both locale files and reviewed current PR metadata; there are no Discussions, linked fixes, owners, or duplicates.
I am not proposing a code/document patch because the public guide begins by saying open-source Lynx currently lacks canvas support, while the example describes an internal environment. Resolving that platform contract requires maintainer confirmation rather than a mechanical copy edit.
Documentation URL
Cross-terminal_and_Developer_Ecology/lynx.mdDescription
The Lynx guide contains several signs that its usage section was copied from a different platform and is not self-consistent:
js,ttml, andttssinstructions explain using VChart in a Feishu widget, even though this is the Lynx guide.index.jsexample retains Chinese-only comments throughout lines 146-156 and later event handling.resolve.enable INodeCache; the Chinese page usesresolve.enableINodeCache.Expected: clarify whether the TTML/TTSS/Card example is really the supported Lynx integration. If it is, name the correct Lynx environment and translate the remaining English comments; if it is not, replace it with a verified Lynx example. Correct the option token to the actual configuration key.
I fetched all 4,627 open/closed issues and pull requests and found no matches for
enable INodeCacheor the Feishu-widget wording in a Lynx report. I also compared both locale files and reviewed current PR metadata; there are no Discussions, linked fixes, owners, or duplicates.I am not proposing a code/document patch because the public guide begins by saying open-source Lynx currently lacks canvas support, while the example describes an internal environment. Resolving that platform contract requires maintainer confirmation rather than a mechanical copy edit.