[Bug]: Missing rename popup in extract to local variable code action

[mindula]

Description

Consider the following scenario,

Screen.Recording.2023-05-29.at.08.03.21.mov

Steps to Reproduce

import ballerina/http;

final http:Client ep = check new ("https://localhost:9091/items",
    auth = {},
    secureSocket = {
        cert: "./resources/public.crt"
    });

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Editor

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[mindula]

Currently, when calculating the rename position, we get the line range of the extractable node and increment the line number by 1. This approach gives the correct rename position when the values are on a single line. However, if the values are defined on multiple lines, the correct rename position can not be identified. Hence, we need to figure out an appropriate method to calculate the rename position. The same behaviour can also be seen in the Extract to constant code action.

[github-actions]

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.