Update Lisa

[key10iq]

Description

My update adds the ability to configure the indicator LEDs function directly from VIA

Types of Changes

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

Issues Fixed or Closed by This PR

• Updated keyboard - keyten/lisa

Checklist

• [x] My code follows the code style of this project: C, Python
• [x] 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.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[waffle87]

Unfortunately this cannot be accepted, as custom VIA indicator code is not currently not accepted to the qmk_firmware repository due to the maintenance burden it poses.

[key10iq]

Unfortunately this cannot be accepted, as custom VIA indicator code is not currently not accepted to the qmk_firmware repository due to the maintenance burden it poses.

Is this considered a custom VIA code? https://github.com/key10iq/keyboards/blob/Lisa/v3/keyten/lisa/lisa.json

This is controlled like a regular multilayout

[zvecr]

From the PR checklist:

keyboard updates and refactors (eg. to data driven) must go through develop to reduce master -> develop merge conflicts

And with https://docs.qmk.fm/ChangeLog/20240526#migration-of-via-keymaps-to-via-team-control, we would certainly not be accepting any further keyboard level via customisation.

[key10iq]

Got it, thanks