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.

Sign up for GitHub

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

Jump to bottom

[Core] use IS_EVENT macro instead of !IS_NOEVENT #19366

Merged
merged 1 commit into from
Dec 17, 2022
Merged

[Core] use IS_EVENT macro instead of !IS_NOEVENT #19366

merged 1 commit into from
Dec 17, 2022

Conversation

KarlK90
Copy link
Member

@KarlK90 KarlK90 commented Dec 17, 2022

Description

Just a small readability improvement.

Types of Changes

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

Issues Fixed or Closed by This PR

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).

@github-actions github-actions bot added the core label Dec 17, 2022
@KarlK90 KarlK90 requested a review from a team December 17, 2022 12:21
@zvecr zvecr merged commit 8598490 into qmk:develop Dec 17, 2022
omikronik pushed a commit to omikronik/qmk_firmware that referenced this pull request Jan 22, 2023
@KarlK90 @omikronik
Introduce IS_EVENT instead of !IS_NOEVENT (qmk#19366)
aeff04e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@zvecr zvecr zvecr approved these changes

Assignees
No one assigned
Labels
core
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@KarlK90 @zvecr