1# Change Log 2 3## [1.3.3] 4 5- The `pigweed.activateBazeliskInNewTerminals` option has been set to a default 6 of `false` because, as currently implemented, this feature interferes with 7 interactive tasks like flashing scripts and `pw_console`. 8 9## [1.3.2] 10 11- When you manually run `Pigweed: Refresh Compile Commands`, we now show a 12 progress notification so you know what's happening. 13 14- Synchronizing settings between the committed settings (`settings.shared.json`) 15 and the local settings (`settings.json`) is now dramatically faster (pretty 16 much instantaneous). 17 18- If you manually change the code analysis target by editing a settings file 19 directly, the effect will now be the same as if you had run the 20 `Pigweed: Select Code Analysis Target`. 21 22## [1.3.1] 23 24- Newly-launched integrated terminals will now automatically have the 25 configured path to `bazelisk` patched into the shell path. This is essentially 26 running `Pigweed: Activate Bazelisk in Terminal` automatically when launching 27 a new integrated terminal. This behavior can be disabled by setting 28 `pigweed.activateBazeliskInNewTerminals` to `false` in your settings. 29 30## [1.3.0] 31 32- You can now disable `clangd` code intelligence for files that are not built 33 as part of the target you're using for code intelligence. Why would you want 34 to do this? By default, `clangd` will try to *infer* compile commands for 35 files that won't actually be built, producing incorrect and misleading code 36 intelligence information ([see this doc](https://pigweed.dev/pw_ide/guide/vscode/code_intelligence.html#inactive-and-orphaned-source-files) 37 for more information). 38 39- File indicators in the file explorer and file tabs now show each file's status 40 with regard to the currently-selected code intelligence target. For example, 41 files that are not part of the target's build are faded out so you're not 42 surprised when they don't show code intelligence ([learn more here](https://pigweed.dev/pw_ide/guide/vscode/code_intelligence.html#inactive-and-orphaned-source-files)). 43 44- We now provide a mechanism for shared settings that can be committed to source 45 control, along with personal user settings that also include ephemeral editor 46 state, like the currently-selected code intelligence target and `clangd` 47 settings. [Check out this doc](https://pigweed.dev/pw_ide/guide/vscode/#project-settings) 48 for more details. 49 50- Output from the compile commands refresh process is now streamed in real-time 51 to the Pigweed output window. 52 53- The method of finding the path to `clangd` in the toolchain brought in by 54 Bazel is now more robust and reliable. 55 56- Bundled tools (`bazelisk` and `buildifier`) now have their paths automatically 57 updated whenever a new version of the extension is installed. 58 59## [1.1.4] 60 61- Properly supports [bzlmod](https://docs.bazel.build/versions/5.1.0/bzlmod.html) 62 projects. 63 64## [1.1.3] 65 66- Fixes a project root inference bug. 67 68## [1.1.2] 69 70- Output from the compile commands refresh process is now streamed to the 71 Pigweed output panel in real time, allowing you to monitor progress in the 72 same way you would if you had invoked it from the terminal. Before, the output 73 was just buffered and sent to the output window when complete. 74 75- The extension will no longer attempt to infer the project root if one is set 76 manually via [pigweed.projectRoot](https://pigweed.dev/pw_ide/guide/vscode/#pigweed.projectRoot). 77 This prevents spurious failures if you have an uncommon project structure but 78 have pointed the Pigweed extension in the right direction by specifying the 79 project root. 80 81- Missing command implementation stubs for bootstrap-based projects are no 82 longer missing. 83 84## [1.1.1] 85 86- Adds support for [fish shell](https://fishshell.com/) to the 87 `Pigweed: Activate Bazelisk in Terminal` command (in addition to the existing 88 support for `bash` and `zsh`). 89 90## [1.1.0] 91 92- Adds `Pigweed: Activate Bazelisk in Terminal`: This command will modify the 93 `$PATH` in your active integrated terminal to include the configured path to 94 Bazelisk. This allows you to run Bazel actions via editor commands or via 95 `bazelisk ...` invocations in the terminal, while working in the same Bazel 96 environment. 97 98## [1.0.0] 99 100- Initial release of the new and improved Pigweed extension. 101