fix(amazonq): read amazonq-ui.js from servers.zip instead of clients.zip #7982
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Related PR:
As part of changes made to move
amazonq-ui.jsfromclients.ziptoservers.zip, we now need to load the LSP UI from the correct locations.Solution
lspArtifact.ts- Added backwards compatibility check foramazonq-ui.jsin both locationslspInstaller.ts- Added backwards compatibility logic to check both clients/ and servers/ directoriestypes.ts- Updated comments to show both possible locationsbaseLspInstaller.ts- Updated comments to reflect the changeThe changes maintain backwards compatibility.
Testing
Tested using local build on Mac and Windows with the old and new
.zipsetup and plugin works without issuefeature/xbranches will not be squash-merged at release time.