2024-09-24 08:56:37 +00:00
|
|
|
|
import { _ as _export_sfc, c as createElementBlock, o as openBlock, a8 as createStaticVNode } from "./chunks/framework.B9AX-CPi.js";
|
2024-06-02 02:43:43 +00:00
|
|
|
|
const __pageData = JSON.parse('{"title":"QMK Breaking Changes - 2022 November 26 Changelog","description":"","frontmatter":{},"headers":[],"relativePath":"ChangeLog/20221126.md","filePath":"ChangeLog/20221126.md"}');
|
|
|
|
|
|
const _sfc_main = { name: "ChangeLog/20221126.md" };
|
|
|
|
|
|
const _hoisted_1 = /* @__PURE__ */ createStaticVNode('<h1 id="qmk-breaking-changes-2022-november-26-changelog" tabindex="-1">QMK Breaking Changes - 2022 November 26 Changelog <a class="header-anchor" href="#qmk-breaking-changes-2022-november-26-changelog" aria-label="Permalink to "QMK Breaking Changes - 2022 November 26 Changelog""></a></h1><h2 id="notable-features" tabindex="-1">Notable Features <a class="header-anchor" href="#notable-features" aria-label="Permalink to "Notable Features {#notable-features}""></a></h2><h3 id="autocorrect" tabindex="-1">Autocorrect (<a href="https://github.com/qmk/qmk_firmware/pull/15699" target="_blank" rel="noreferrer">#15699</a>) <a class="header-anchor" href="#autocorrect" aria-label="Permalink to "Autocorrect ([#15699](https://github.com/qmk/qmk_firmware/pull/15699)) {#autocorrect}""></a></h3><p><em>@getreuer</em> in their infinite wisdom decided that autocorrect was a feature needed by QMK. As is customary, <em>@drashna</em> adapted it to core and got it into a state that everyone else can use it. See <a href="./../features/autocorrect">Feature: Autocorrect</a> for more ifnormation (grin).</p><h2 id="changes-requiring-user-action" tabindex="-1">Changes Requiring User Action <a class="header-anchor" href="#changes-requiring-user-action" aria-label="Permalink to "Changes Requiring User Action {#changes-requiring-user-action}""></a></h2><h3 id="updated-keyboard-codebases" tabindex="-1">Updated Keyboard Codebases <a class="header-anchor" href="#updated-keyboard-codebases" aria-label="Permalink to "Updated Keyboard Codebases {#updated-keyboard-codebases}""></a></h3><p>The following keyboards have had their source moved within QMK:</p><table><thead><tr><th>Old Keyboard Name</th><th>New Keyboard Name</th></tr></thead><tbody><tr><td>converter/numeric_keypad_IIe</td><td>converter/numeric_keypad_iie</td></tr><tr><td>durgod/k3x0/k310</td><td>durgod/k310</td></tr><tr><td>durgod/k3x0/k320</td><td>durgod/k320</td></tr><tr><td>emptystring/NQG</td><td>emptystring/nqg</td></tr><tr><td>handwired/hillside/46</td><td>hillside/46</td></tr><tr><td>handwired/hillside/48</td><td>hillside/48</td></tr><tr><td>handwired/hillside/52</td><td>hillside/52</td></tr><tr><td>maple_computing/christmas_tree/V2017</td><td>maple_computing/christmas_tree/v2017</td></tr></tbody></table><h3 id="keycodes-overhaul-user-action" tabindex="-1">Keycodes refactoring <a class="header-anchor" href="#keycodes-overhaul-user-action" aria-label="Permalink to "Keycodes refactoring {#keycodes-overhaul-user-action}""></a></h3><p>QMK's keycodes got a very significant overhaul this breaking changes cycle, with the bulk of the work done by <em>@zvecr</em> and <em>@fauxpark</em> -- renaming, reordering, removing has been their focus in this area. In an attempt to standardise interoperation with host applications, keycode values now have strong versioning so that any connected application has confidence that the keys it thinks exist on the board actually match up with what's compiled in. These strongly-versioned keycode definitions are now published online and will not change, so tools that remap keycodes have a reference to work with. In future versions of QMK, any new or changed keycodes will result in a new version specification. See <a href="./../api_docs#qmk-constants">API docs</a> for more information on the published versions if you're writing a tool to manage keycodes.</p><p>In most cases user keymaps in the repository have already been updated to reflect the new naming scheme. In some cases user keymaps outside the repository may strike a missing keycode with the old name -- it's highly likely that the name had already been deprecated for some time, and should have been updated previously.</p><p>See below for the full list of changesets.</p><div class="warning custom-block"><p class="custom-block-title">WARNING</p><p>Keycode aliases have been put in place in most cases to cater for "old names" being mapped to "new names"
|
|
|
|
|
|
const _hoisted_67 = [
|
|
|
|
|
|
_hoisted_1
|
|
|
|
|
|
];
|
|
|
|
|
|
function _sfc_render(_ctx, _cache, $props, $setup, $data, $options) {
|
|
|
|
|
|
return openBlock(), createElementBlock("div", null, _hoisted_67);
|
|
|
|
|
|
}
|
|
|
|
|
|
const _20221126 = /* @__PURE__ */ _export_sfc(_sfc_main, [["render", _sfc_render]]);
|
|
|
|
|
|
export {
|
|
|
|
|
|
__pageData,
|
|
|
|
|
|
_20221126 as default
|
|
|
|
|
|
};
|
