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

Remove always enabled effects from lighting animation list #22992

Merged
merged 2 commits into from
Jan 31, 2024

Conversation

zvecr
Copy link
Member

@zvecr zvecr commented Jan 31, 2024

Description

Always enabled, so adding the config line is completely pointless.

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

@zvecr zvecr changed the title Remove 'solid_color' from animation list Remove unconditional animations from lighting animation list Jan 31, 2024
@zvecr zvecr changed the title Remove unconditional animations from lighting animation list Remove always enabled effects from lighting animation list Jan 31, 2024
@zvecr zvecr mentioned this pull request Jan 31, 2024
14 tasks
@zvecr zvecr merged commit bfcf3c1 into develop Jan 31, 2024
2 of 3 checks passed
nuess0r pushed a commit to nuess0r/qmk_firmware that referenced this pull request Sep 8, 2024
* Remove 'solid_color' from animation list

* Remove 'solid'/'none' from animation list
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants