[Documentation] Lynx guide mixes Feishu instructions and untranslated content
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 221
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 26
Description
Documentation URL
- https://www.visactor.io/vchart/guide/tutorial_docs/Cross-terminal_and_Developer_Ecology/lynx
- English and Chinese
Cross-terminal_and_Developer_Ecology/lynx.md
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, andttssinstructions explain using VChart in a Feishu widget, even though this is the Lynx guide. - The English complete
index.jsexample 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 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 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.
Contributor guide
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
Read the English and Chinese Cross-terminal_and_Developer_Ecology/lynx.md files and compare the usage and troubleshooting sections. First get maintainer confirmation about whether the TTML/TTSS/Card example targets a supported Lynx environment. Done means the guide contains a verified Lynx example or clearly justified integration, translated English comments, and the correct configuration key.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100