Skip to content

refactor: Use GraphQL interface for project AI ban

Allen Cook requested to merge 1218-vs-code-extension-should-not-supply-code-suggestions-on-disabled-projects into main

Description

Because the group-level settings for disabling duo features will use cascading settings the GraphQL setting project >> duoFeaturesEnabled will be equivalent to /code_suggestions/enabled when those features are implemented.

Since implementing the GraphQL check will solve the problems with WebIDE and catching a 403 from the REST API, this MR switches to using the GraphQL project >> duoFeaturesEnabled

Related Issues

Relates to Granular control to enable/disable Code Suggest... (&11950 - closed)

How has this been tested?

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation
  • Chore (Related to CI or Packaging to platforms)
  • Test gap

Closes #1218 (closed)

Edited by Tomas Vik

Merge request reports