Follow up to a small issue Bob identified in #12735. When IntelliSense is disabled, the existing behavior is to fall back to also disabling the related files API and registering the getIncludes command as a no-op. However, that wouldn't correctly test the eventual migration we want where the getIncludes command goes away entirely. I changed this to explicitly check the experiment state on the IntelliSense disabled path too.
No need to re-spin any insiders builds for this -- it can go into the next release.
Follow up to a small issue Bob identified in #12735. When IntelliSense is disabled, the existing behavior is to fall back to also disabling the related files API and registering the
getIncludescommand as a no-op. However, that wouldn't correctly test the eventual migration we want where thegetIncludescommand goes away entirely. I changed this to explicitly check the experiment state on the IntelliSense disabled path too.No need to re-spin any insiders builds for this -- it can go into the next release.