If your backend exposes it, allowing a key to be retrieved by either name ("a" maps to "a" on azerty, usecase: press "n" to toggle normals) or position ("a" maps to "q" on azerty, usecase: wasd movements) would be a huge upgrade for non-qwerty users :)

In js I think it's done by comparing to either event.key or event.code. Although event.code names are a little strange ("KeyA" for "a") – and it could be possible to map them to something more analogous to event.key names ("a") since they are less than 255 of them – exposing them as is is still a good (and probably more sane) start.

Name survey:

• js: event.key vs event.code
• sdl2: event.key.keysym.sym vs event.key.keysym.scancode (of type SDL_Keycode vs SDL_Scancode)
• sdl3: event.key.key vs event.key.scancode (of type SDL_Keycode vs SDL_Scancode)
• glfw: void key_callback(GLFWwindow* window, int key, int scancode, ...)
• godot4: InputEventKey.keycode vs InputEventKey.physical_keycode
• unity: old: GetKey(string name) vs GetKey(KeyCode key), new: ? vs Keyboard.current.<key>
• etc.

-> we could call that playground::KEY_NAME and playground::KEY_CODE (removed _INPUT since it doesn't appears in mouse either).