Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix extensionConfiguration/change type, respect authStatus from cody … (
#2629) cherry picking (#2623) ## Changes 1. Bumped cody commit to match the one from `jb-v7.1.x` branch 2. Fixed `"extensionConfiguration/change"` endpoint type - issue was introduced [there](8ea63fc) 3. For the sake of correctness I also added check of returned auth state and if auth fails I set the token as invalid. ## Test plan 1. Run IDE 4. Remove all account in the cody settings 5. Login panel shoul appear 6. Sign in to enterprise account 7. Make sure chat panel appears and in the account panel enterprise acc is shown 8. Remove all account in the cody settings 9. Login panel should appear 10. Sign in to free dotcom account 11. Make sure chat panel appears and in the account panel free acc is shown ## Test plan <!-- All pull requests REQUIRE a test plan: https://sourcegraph.com/docs/dev/background-information/testing_principles Why does it matter? These test plans are there to demonstrate that are following industry standards which are important or critical for our customers. They might be read by customers or an auditor. There are meant be simple and easy to read. Simply explain what you did to ensure your changes are correct! Here are a non exhaustive list of test plan examples to help you: - Making changes on a given feature or component: - "Covered by existing tests" or "CI" for the shortest possible plan if there is zero ambiguity - "Added new tests" - "Manually tested" (if non trivial, share some output, logs, or screenshot) - Updating docs: - "previewed locally" - share a screenshot if you want to be thorough - Updating deps, that would typically fail immediately in CI if incorrect - "CI" - "locally tested" --> Co-authored-by: Piotr Kukiełka <[email protected]>
- Loading branch information