Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for keymaps array to be implemented in a file other than $(KEYMAP_C) #17559

Merged
merged 1 commit into from
Jul 4, 2022

Conversation

tzarc
Copy link
Member

@tzarc tzarc commented Jul 4, 2022

Description

Some weird keymap generation going on with the miryoku keymaps -- they weren't actually part of the normal keymap.c file, but rather specified elsewhere.

This adds the ability to specify a different file to include into the introspection code.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@tzarc tzarc requested a review from a team July 4, 2022 04:56
@drashna drashna requested a review from a team July 4, 2022 05:14
@tzarc tzarc force-pushed the allow-non-keymap_c-introspection branch from 4a7cd50 to c29da06 Compare July 4, 2022 05:17
@tzarc
Copy link
Member Author

tzarc commented Jul 4, 2022

Hopefully addresses instances like the followup comments on #17229.

@fauxpark
Copy link
Member

fauxpark commented Jul 4, 2022

TBH I'm not 100% convinced that allowing this aligns with the data driven direction in the first place. Just my 2c.

@masiullah
Copy link

This worked for me, thank you

@tzarc
Copy link
Member Author

tzarc commented Jul 4, 2022

TBH I'm not 100% convinced that allowing this aligns with the data driven direction in the first place. Just my 2c.

100% agree, but right now the introspection breaks things written that way. We're kicking the can down the road while we sort out DD.

@tzarc tzarc merged commit 0e5d671 into qmk:develop Jul 4, 2022
@tzarc tzarc deleted the allow-non-keymap_c-introspection branch July 4, 2022 22:58
nolanseaton pushed a commit to nolanseaton/qmk_firmware that referenced this pull request Jan 23, 2023
@sigprof sigprof mentioned this pull request Jan 29, 2023
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants