It appears that when navigating through syntax trees of great intricacy, ts-context would expend an excessive amount of time collecting (and rendering) all "candidate nodes" from here to the root of the tree when the cursor goes deep into a particular "branch", given our current settings. This PR limited max_lines to 3, as IMO we seldom need hierarchical information about nodes that are too distant from the current one in practice, and 3 is also the optimal value I've found in recent trials that strikes a balance between the amount of practical information and performance penalties lol
It appears that when navigating through syntax trees of great intricacy,
ts-context
would expend an excessive amount of time collecting (and rendering) all "candidate nodes" from here to the root of the tree when the cursor goes deep into a particular "branch", given our current settings. This PR limitedmax_lines
to 3, as IMO we seldom need hierarchical information about nodes that are too distant from the current one in practice, and3
is also the optimal value I've found in recent trials that strikes a balance between the amount of practical information and performance penalties lol