Structured drafts
Jianlai tutorial 23: type a JSON object and check strings, numbers and paired symbols
Type an original two-member JSON object with Jianlai in an ordinary draft, delivering its source, a member-type ledger and one repaired counterexample. Verify accurate entry separately from external parsing. Jianlai supplies text input; it is not presented as a JSON editor, parser or data-upload tool.
On this page
Type an original two-member JSON object with Jianlai in an ordinary draft, delivering its source, a member-type ledger and one repaired counterexample. Verify accurate entry separately from external parsing. Jianlai supplies text input; it is not presented as a JSON editor, parser or data-upload tool.
1. Draw the two-member structure first
On paper, define an exercise object with only a name label and a count. The name contains the example brand spelling and the numeric value is two; there are no accounts, tokens or server addresses. Make separate columns for member name, value and value type. Both member names are strings; only the second value is numeric. The code block supplies the sole raw line, excluding comments, surrounding explanations and the fences themselves. A plain-text host can retain the characters without understanding the structure. Parsing, if needed, requires a separately identified tool. Establish that boundary before bringing in unrelated network interfaces or real application configuration merely to demonstrate a keyboard. All entry in this lesson can remain in a local draft.
2. Enter the shell and then each member
Enter an ordinary editable area, confirm Jianlai is active, and use the installed English-letter and symbol layouts to type the target. You may complete the opening brace and first member before the separator comma, second member and closing brace. No unpublished shortcut for generating paired symbols is assumed. Keep ASCII straight double quotes around member names and the example brand, but not around the numeric two. Each of the two colons connects its own member name and value. The sample has no spaces. Although the standard allows whitespace in certain positions, this exercise first requires literal fidelity. Commit composition before inspecting body text; an English word still pending in the candidate area is not proof that the object is fully entered.
{"name":"Jianlai","count":2}
3. Check symbol roles, not just totals
Check one outer pair of braces, one comma separating two members and two colons following the correct member names. There are six ASCII double quotes: two pairs around names and one pair around the first value. The final number has no quote pair. A total of six is insufficient unless each member name’s closing quote is correctly placed before its colon and the separator comma is outside strings. Point through the literal sample in segments. Record fullwidth colons, curly quotes, single quotes or lookalike brackets as character differences; theme colors are not a syntax test. Put fault locations in an external checklist rather than inserting explanations into the JSON line, where they would introduce characters outside the target.
4. Read values and types back explicitly
For the manual interpretation, the first member’s value is a case-sensitive string matching the sample, and the second member’s value is numeric two. Putting straight double quotes around two may still produce syntactically valid JSON, but changes the value to a string and fails this task’s contract. Thus “parses successfully” and “matches the data agreement” are separate conditions. Check the exact member-name spelling too; recognizable intent does not excuse altered letters or case. This object has just two distinct names, so no duplicate-name behavior is involved. Do not casually add a third member to extend the exercise. Keep a two-row type ledger as a clear reference for any later tool output.
name: string = Jianlai
count: number = 2
5. Locate and repair a trailing-comma fault
Copy the correct line into a separate practice area and deliberately add one comma just before the final closing brace. Keep the correct reference untouched. Under JSON object syntax, a comma separates members and must be followed by another member; the trailing comma is not harmless decoration. A permissive language or tool accepting it does not make it standard JSON. Circle the surplus symbol manually, then use host selection or insertion-point controls to remove only that comma. Verify that both members and their quotes remain intact. Return to the sole target without also reordering members or adding spaces. If a number or brace is accidentally deleted, stop repeated deletion and rebuild the practice copy from the reference before checking again.
6. Keep external parser reports separate
If a trusted local JSON tool is available, give it the correct nonprivate sample and record the actual report. Check for an object with exactly two members and the specified types. Do not include article fences, the member ledger or words such as “parsing passed” in its input. If it offers a permissive mode, identify whether the check uses standard JSON. Without a tool, retain the manual structure check and mark parsing as not run; no online validator search or upload of other configuration is necessary. Acceptance applies to this input only, not every future object, and does not establish JSON validation as a Jianlai feature. Keep actual reports separate from paper expectations. Save any pretty-printed output separately rather than replacing the literal input reference.
7. Diagnose characters, syntax and types separately
For an error, first compare straight quotes and ASCII punctuation, then brace pairing, separator comma and colon positions, and finally value types and member spelling. If characters look correct but output is wrong, consult the type ledger instead of first changing skins or reinstalling the keyboard. A string containing two is not numeric two made different by a font. If the host curls quotes, record whether it happens at commit, paste or save-and-reopen, then retry in a copy that preserves source text. A tool’s reported line and column refer to that particular input, not a universal Jianlai error code. Repair one explained discrepancy at a time, keeping each raw line associated with its own report so later output is not attributed to earlier text.
8. Save a minimal reviewable package
Retain the clean target line, two-member type ledger, trailing-comma repair record and actual verification state. Check source characters first, standard-syntax expectations second and whether an external tool really ran last. That order locates a failure at a specific layer. Close and reopen the host and check that source and explanations have not merged into one line. If that step is not performed, leave it pending rather than claiming persistence. Annotate the keyboard state and host name and reuse the same sample for a later reproduction. Backslashes, escaped newlines or deeper objects would require a new agreement and example; passing two simple members cannot substitute for checking more complex content.
Related guides and sources
ASCII punctuation contracts; Local revision and neighbour check.
Checked on 17 November 2026: Apple’s Finland lookup and China lookup both list Jianlai 1.0.5, requiring iOS / iPadOS 16.0 or later. The official store describes themes, backgrounds, fonts and multilingual input. Use controls actually present in the installed version; system editing and host processing are distinguished separately. These are repeatable instructions and paper expectations, not claims of completed device input, host compatibility or format-parser tests.
Method references: RFC 8259 JSON grammar; Apple text editing guide.