lint lines in package.ludic - one_statement, max_file_lines, max_function_lines, max_comment_lines, max_header_lines, paths, baseline - checked by ludic-fmt --check <files> and ludic-fmt --lint (the project), at the line; a baseline ratchet lets a rule arrive in a codebase that breaks it (--init-baseline), lowered as it is fixed. check-impl reads the alias declarations too (it had been blind to every namespace L6 moved out of the compiler), and eight methods get their pages; a test holds the formatter to keeping type arguments together (L5). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
24 lines
600 B
Markdown
24 lines
600 B
Markdown
---
|
|
id: input-text
|
|
name: Input.text
|
|
category: input
|
|
kind: namespace-method
|
|
tokens: Input.text
|
|
sig: Input.text() -> string
|
|
tip: The text typed this frame.
|
|
order: 61
|
|
ns: Input
|
|
member: text
|
|
---
|
|
|
|
What the keyboard layout, the modifiers and any dead key produced this frame, as UTF-8 - the only right way to fill a name field, because it is the characters the player meant rather than the keys they pressed (a binding reads keys by position; text reads what they type). Empty in a headless run.
|
|
|
|
```ludic
|
|
program Name {
|
|
entry {
|
|
var name = ""
|
|
name = name + Input.text()
|
|
print(name)
|
|
}
|
|
}
|
|
```
|