Resolve keyboard_aliases when processing keyboard make targets #24834
+41
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The aim is to minimise disruption to end users while we continue the deprecation process of
DEFAULT_FOLDER
.Implementation is somewhat less than ideal, but hopefully its only temporary while
DEFAULT_FOLDER
handling still exists.Enabled keyboard_aliases.hjson values to be used, for example
While still allowing keyboards with
DEFAULT_FOLDER
to compile as beforeTypes of Changes
Issues Fixed or Closed by This PR
Checklist