Tobias Tengler

Does this only happen, if you make changes to your GraphQL definitions after you've started the LSP? Maybe it's related to https://github.com/facebook/relay/issues/4447

This is indeed very overdue @alunyov @captbaritone I see that the last runs of the extension publish workflow weren't successful: https://github.com/facebook/relay/actions/workflows/vscode.yml Is this the only blocker or are there other...

Locally I'm able to at least package the extension via `yarn --ignore-engines vsce package`. Could one of you maybe run the Action again? In the best case we get a...

@captbaritone is this blocked internally? Let me know if there's anything I can do and sorry for all of these PRs that probably don't fit what you're working on atm...

@captbaritone ping 😅 The CI failure seems to be caused by the lock file not being up to date and some unstable features making their way in.

@captbaritone Dammit, missed the release window again 😅 Would still love to get this in though!

@captbaritone to your above points: 1. Yes, not supporting global variables is intentional (for now). 2. If you can provide me with an example of a project that inherits fragments...

@captbaritone I've updated this to also support renaming of proper fragment arguments (variable definitions) now that #4651 is merged. Would love to see this merged. It pains me that this...

I'm able to reproduce this with a test. Working on a fix :)

@captbaritone Fixed!