fix the bug of import {} from "xxx"

[lv2020]

Sorry for the late reply. This is the fix for #1 .

[cassc]

Thanks @lv2020!

• Can you please add a short description about the problem and some example(s) showing the bug you solved?
• I suppose the fix is specifically for import {X, Y, Z} from xxx only? Did you also consider other cases?

[lv2020]

• This is for fixing the bug of incorrect segmentation of the import library. One example would be:

import { IERC20 } from "@openzeppelin/contracts/token/ERC20/IERC20.sol";

In the original version, you will get IERC20 } from "@openzeppelin/contracts/token/ERC20/IERC20.sol"; as the library. In my fix, you will get @openzeppelin/contracts/token/ERC20/IERC20.sol.

• Yes, this is only for import {X, Y, Z} from xxx. Because in my collected dataset, I only found this case.

[cassc]

Thanks @lv2020 !