You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regular TextRanges are very expensive. In that cases where text ranges value can be predicted should use computed text ranges. For example:
{ "name": "John Doe" }
where "name" is the whole text range in KeyDeclaration
In the previous case we shouldn't create a new text range just for getting its "pure" value (name itself), but we know exactly that "name" is computed from name and two other quotes. It is easy to calculate.
The text was updated successfully, but these errors were encountered:
Regular TextRanges are very expensive. In that cases where text ranges value can be predicted should use computed text ranges. For example:
In the previous case we shouldn't create a new text range just for getting its "pure" value (name itself), but we know exactly that "name" is computed from name and two other quotes. It is easy to calculate.
The text was updated successfully, but these errors were encountered: