Fix VS Code extension issue by sending a different GQL query for VSCE

Review changes
Download
Patches
Plain diff

Merged Fix VS Code extension issue by sending a different GQL query for VSCE

Overview 5
Commits 10
Pipelines 0
Changes 6

Merged Administrator requested to merge ps/fix-vscode-issue into main 2 years ago

Overview 5
Commits 10
Pipelines 0
Changes 6

Created by: philipp-spiess

A recent change changed one of the GraphQL queries that the VS Code extension is using to add a new field that was only recently added to the GraphQL backend (c.f. here).

This unfortunately is not available on "older" server versions including 3.42.1. This means that every person that updates their VS Code extension release now and is on an on-prem server that lags a bit behind will see the search broken.

We do not yet have a system to get the server version and make decisions based on it so I decide to fix it by reverting to the previous query in the VS Code environment (the backend is written in a way that it can handle older clients, just not the other way around).

Test plan

I verified that this fixes the VSCE issue by running a query against 3.42.1.

App preview:

Web
Storybook

Check out the client app preview documentation to learn more.

Merge request reports

Activity

Filter activity

Approvals
Assignees & reviewers
Comments (from bots)
Comments (from users)
Commits & branches
Edits
Labels
Lock status
Mentions
Merge request status
Tracking

Please register or sign in to reply

0 Assignees

None

Select assignees

0 Reviewers

None

Request review from

Labels

bug cla-signed vscode-extension

Select labels

Manage project labels

Milestone

Integrations 16

Integrations 16 (expired)

None

Time tracking

No estimate or time spent

1 Participant

There are currently no pipelines.

To run a merge request pipeline, the jobs in the CI/CD configuration file must be configured to run in merge request pipelines and you must have sufficient permissions in the source project.