Duplicated code to handle (sequences of) key presses

[rodrigogiraoserrao]

There is definitely some duplicated code in the codebase with regards to how keys are handled and converted from codepoints to events.
Consider these four instances, which are not necessarily the only ones:

textual/src/textual/app.py

Lines 830 to 837 in be85063

	if len(key) == 1 and not key.isalnum():
	key = (
	unicodedata.name(key)
	.lower()
	.replace("-", "_")
	.replace(" ", "_")
	)
	original_key = REPLACED_KEYS.get(key, key)

textual/src/textual/_xterm_parser.py

Lines 253 to 264 in be85063

	elif len(sequence) == 1:
	try:
	if not sequence.isalnum():
	name = (
	_unicode_name(sequence)
	.lower()
	.replace("-", "_")
	.replace(" ", "_")
	)
	else:
	name = sequence
	name = KEY_NAME_REPLACEMENTS.get(name, name)

textual/src/textual/keys.py

Line 250 in be85063

upper_original = original_key.upper().replace("_", " ")

textual/src/textual/keys.py

Lines 266 to 269 in be85063

	if not character.isalnum():
	key = unicodedata.name(character).lower().replace("-", "_").replace(" ", "_")
	else:
	key = character

I see lots of very similar bits and bobs, and things like multiple attempts at normalising key/codepoint names, etc.
These should probably be refactored into methods that we can use that will ensure consistency.

Related to: #1815

[github-actions]

Don't forget to star the repository!

Follow @textualizeio for Textual updates.