[all-commits] [llvm/llvm-project] 19ecde: [lldb-dap] Rename `enableDisplayExtendedBacktrace`...

[Adrian Vogelsgesang via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 19ecdedcd2b7fb44689ce3cd59a6a078539eef3f
      https://github.com/llvm/llvm-project/commit/19ecdedcd2b7fb44689ce3cd59a6a078539eef3f
  Author: Adrian Vogelsgesang <avogelsgesang at salesforce.com>
  Date:   2024-09-22 (Sun, 22 Sep 2024)

  Changed paths:
    M lldb/packages/Python/lldbsuite/test/tools/lldb-dap/dap_server.py
    M lldb/packages/Python/lldbsuite/test/tools/lldb-dap/lldbdap_testcase.py
    M lldb/test/API/tools/lldb-dap/extendedStackTrace/TestDAP_extendedStackTrace.py
    M lldb/tools/lldb-dap/DAP.cpp
    M lldb/tools/lldb-dap/DAP.h
    M lldb/tools/lldb-dap/README.md
    M lldb/tools/lldb-dap/lldb-dap.cpp
    M lldb/tools/lldb-dap/package.json

  Log Message:
  -----------
  [lldb-dap] Rename `enableDisplayExtendedBacktrace` (#109521)

The `enable` prefix is a filler word which adds no additional
information. Rename the setting to `displayExtendedBacktrace`

Given that this setting was only introduced a month ago, and that there
has not been any release since then, I assume that usage is still rather
low. As such, it should be fine to not provide backwards-compatibility
workarounds.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications