Daniel Veihelmann

I have the same problem in a "real" application, not just the demo.

Until this has been merged, it seems a fix is to set the following env variables: ``` PROTOCOL_HEADER=x-forwarded-proto HOST_HEADER=x-forwarded-host ```

+1. This plugin is indeed _awesome_ , but this is unfortunately a deal breaker for me...

We ran into this as well. In our case, **we could track this down to the use of `ServerProperties.TRACING` and `ServerProperties.TRACING_THRESHOLD`**, which we set for debugging purposes. In our case,...

Excactly @jansupol , it's 100% reproducible. We use the following Jersey packages: > compile 'org.glassfish.jersey.containers:jersey-container-servlet-core:2.28' > compile 'org.glassfish.jersey.containers:jersey-container-jetty-http:2.28' > compile 'org.glassfish.jersey.inject:jersey-hk2:2.28' > compile 'org.glassfish.jersey.ext:jersey-entity-filtering:2.28' > compile 'org.glassfish.jersey.media:jersey-media-multipart:2.28' running with a...

Still the main blocker for our adoption of Bun. Maybe exposing the C API as suggested by @Vanilagy could be a quick(er) fix, @Jarred-Sumner ?

Will be fixed with #11 . The solution is to run VS Code's formatter after the new component has been extracted.

Hi @proverbial-ninja , do you have any thoughts on this and the PR? Is this project still maintained? :slightly_smiling_face:

Any news here @proverbial-ninja ? I could also create an independent fork of this plugin as I find it really useful

You can configure VS Code to remove unused imports on save, so it will be quite easy to fix the original file. Ideally, extracting a component would also check if...