docs: close out javascript upstream tracking issues - #2184
Merged
Conversation
squid-protocol
force-pushed
the
fix/tri-comparison-javascript-flow-types
branch
from
August 23, 2026 21:04
6cc8660 to
207aeac
Compare
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR finalizes the documentation and ledger adjustments for the upstream
ctagsandtree-sitterlimitations in JavaScript tracking issues 2162 and 2163.ctags_reader.py(Issue Upstream tracking: ctags loses property keys for function-valued object literals in JavaScript #2162).credit_tools: ["gitgalaxy"]) for correctly parsing functions that both AST tools choke on due to Flow type annotations, and regenerates the chart (Issue Upstream tracking: tree-sitter-javascript fails on Flow type annotations and drops subsequent functions #2163).Resolves #2162
Resolves #2163