Skip to content

v2 is still pretty bad #147

@kjjd84

Description

@kjjd84

im not sure why you changed v1 so much, it was working amazingly well

v2 has tons of issues still. you resolved most of them, but its still not as good as v1.

for example, i'm regularly getting warnings that classes aren't used.

also, this version seems to eat at my ram for no good reason. to the point where sometimes i have to force reload vscode. if a class is very large, vscode struggles to even scroll through it whereas this never used to happen before.

i dont want to seem ungrateful, i appreciate the work you have put into this extension over the years. however, if these issues cannot be resolved then i will just have to fork the last version of v1 and release it.

see attached screenshot of what i'm talking about, this is just 1 example

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions