199cb577c5
Answer stability round 1: unexport the grammar's helpers the root never calls, and drop CheckName's note of its callers
lilleman2026-10-05 12:26:43 +02:00
350514b60e
Test a calc reading one operand twice
lilleman2026-10-05 12:25:32 +02:00
c97ed3612b
Answer architecture round 2: name the step up in item 110
lilleman2026-10-05 12:25:22 +02:00
6fd7da19e5
Answer architecture round 1: calls carry no operands in the grammar, ParseCalc returns its operands, one empty-segment check, sorted token kinds, and file items 110 and 111
lilleman2026-10-05 12:25:22 +02:00
3479f9cf98
Test a calc's operand list, one empty-segment check, and an empty segment after a step up
lilleman2026-10-05 12:25:22 +02:00
5e56b44dfa
Drop item 98 from the plan, list internal/grammar in the Layout, and name the grammar in the decisions citing item 98
lilleman2026-10-05 12:11:36 +02:00
c2f2e86735
Move how the template language is written into internal/grammar
lilleman2026-10-05 12:11:36 +02:00
41292f9d89
Test internal/grammar, and allow the root to import it
lilleman2026-10-05 12:06:43 +02:00
46895151c8
Answer prose round 1: plainer sentences in the two decisions, no provenance in items 108 and 109, and shorter comments in drawstate, render and format
lilleman2026-10-05 11:57:58 +02:00
376ab29457
Answer architecture round 2: read go.mod's module path as its first field, unquoted, and fail when no import matches it
lilleman2026-10-05 11:54:51 +02:00
1d0fe9f555
Answer architecture round 1: read the module path from go.mod, keep the randomness behind State's methods, rename the field drawState and the counter Seq, and file items 108 and 109
lilleman2026-10-05 11:52:10 +02:00
ddc3193593
Drop item 97 from the plan, list internal/drawstate in the Layout, and name the draw state in the decisions citing item 97
lilleman2026-10-05 11:45:19 +02:00
2d9c315e75
Move the seeded randomness and the {seq()} counters into internal/drawstate
lilleman2026-10-05 11:43:45 +02:00
4a680f03b3
Test internal/drawstate and the module packages each package may import
lilleman2026-10-05 11:43:04 +02:00
b1d26cd999
Answer prose round 2: state the merge gate as AGENTS.md does, name the draw-afresh change, and rewrap the engine decision
lilleman2026-10-05 11:39:04 +02:00
e17660e8ba
Answer prose round 1: state the gate once in item 5, title the engine decision by what this commit holds, and plainer wording across items 97 to 107 and the decisions
lilleman2026-10-05 11:37:59 +02:00
b6f3df2c9f
Answer architecture round 2: carry the engine table on its rows table, name the imports items 99 and 102 need, and correct the engine decision's premise
lilleman2026-10-05 11:35:23 +02:00
e383005f6c
Answer architecture round 1: settle DataType in item 99, own the table family in internal/rows, fold items 7 and 48 into the restructure, and hold the other 0.1.0 items behind item 5
lilleman2026-10-05 11:32:16 +02:00
2ce8afd0fe
Plan the restructure as items 97 to 107: one writer per value, what stands alone in internal/, the engine in the root until item 107
lilleman2026-10-05 11:08:01 +02:00
87106f450a
Answer product-owner round 4: say a column reading a bound column of its own record is that column
lilleman2026-10-05 10:12:16 +02:00
7a4f95ce15
Record the maintainer's yes on item 96
lilleman2026-10-05 10:09:31 +02:00
bf81c38315
Answer prose round 2: one wording for what a binding binds, the calc exception scoped in the decision, and rewrapped lines
lilleman2026-10-05 10:05:14 +02:00
f89ffd1b73
Answer stability round 3, product-owner round 3 and prose round 1: a column reading a bound column takes its datatype and null, a column bound in part draws afresh, and plainer wording across the README, decisions, plan and errors
lilleman2026-10-05 10:04:11 +02:00
dfde34556e
Answer product-owner round 2: render a record column a name binds whole from the pick
lilleman2026-10-05 09:56:05 +02:00
8d82759520
Answer stability round 1 and product-owner round 1: refuse a field binding read once from above its binder, word the self-read refusal plainly, say how a bound field's column keeps the pick, and ask item 96
lilleman2026-10-05 09:54:38 +02:00
f4a05fbb36
Answer architecture round 3: walk a table's row node in the cycle check, record where the read-once spelling meets an inline refusal, and cite goal 5.2 for a path tag drawing afresh
lilleman2026-10-05 09:42:54 +02:00
938bbb5c43
Answer architecture round 2: refuse a self-read only inside what the binding lands on, fix the struct.go Layout line, move loneRef beside its caller, and widen item 83 to the link passes
lilleman2026-10-05 09:41:20 +02:00
1a15a139c8
Answer architecture round 1: refuse a name read inside the field it binds, check every scope's cycles, build a column read in one pass, drop the implicit struct pick for names across tags, and state the fresh-draw rule once
lilleman2026-10-05 09:39:18 +02:00
a45edf8fb5
Document fresh draws and named picks, revise the decisions the restructure ends, and close items 4 and 87
lilleman2026-10-05 09:12:34 +02:00
5a3abc325f
Hold the allocation gate to what both supported Go versions allocate
lilleman2026-10-05 09:12:34 +02:00
acd1e3ef5a
Re-pin the seeded output for fresh draws
lilleman2026-10-05 09:05:42 +02:00
6aebeebb72
Draw every {…} afresh, keep a pick only by name, and delete drawGroup with the hold and draw fences
lilleman2026-10-05 09:05:35 +02:00
5b23ca7706
Test that every {…} draws afresh and only a name keeps a pick, a field's and a struct's path tags included
lilleman2026-10-05 09:05:35 +02:00
f87807adf7
Update dependency ubuntu to v26
renovate[bot]
2026-10-05 07:37:21 +00:00
972c6deb71
Update python Docker tag to v3.14.8
renovate[bot]
2026-10-05 05:55:44 +00:00
1bd9f58e56
Answer prose round 2 and product-owner round 2: the error shows the spelling to write instead, item 14 only respells the shipped runs, and the key decision says how a code serves goal 5.5
lilleman2026-10-05 07:51:44 +02:00
2bdbb22499
Say why item 14's repeat over {digits(1)} changes nothing
lilleman2026-10-05 07:46:27 +02:00
03577ebca2
Answer prose round 1 and product-owner round 1: give goal 5.7 a test a reader can apply, drop the AGENTS.md copy of it, and cite the key decision to goal 5.5
lilleman2026-10-05 07:43:21 +02:00
0130a46ced
Refuse only a spelling that restates another, and drop item 93
lilleman2026-10-05 02:01:38 +02:00
dc9776061c
Answer stability round 2, product-owner round 2 and prose round 2: state the calc exception in the Names list without an example that loads either way, and one reading for item 93
lilleman2026-10-05 01:20:30 +02:00
426517e66d
Answer stability round 1, product-owner round 1 and prose round 1: say calc reads names in the Functions table, use shipped data in the examples, plainer comments and item wording, mark items 5 and 90 as decision-cited, and ask whether a field spelling of a calc operand is refused
lilleman2026-10-05 01:17:33 +02:00
0743a049d7
Answer architecture round 2: refuse by default where a builtin's operand can be a reference, test the flag against each operand grammar, drop a duplicate test, rename allNeverNumeric, rewrap Computation, and order item 91 after item 4
lilleman2026-10-05 01:10:47 +02:00
94cf741706
Answer architecture round 1: exempt only a calc operand from the read-once refusal, run the name passes from one list, read every operand's leaves, show a name operand in a README example, and plan a path through a name as an operand
lilleman2026-10-05 01:05:20 +02:00
d1b3b05a0c
Close item 71, and suspend scoring for items 4 and 90
lilleman2026-10-05 00:55:35 +02:00
b4052f77f9
Accept a name as a calc operand
lilleman2026-10-05 00:55:13 +02:00
3d320e029c
Test that a calc reads a name as an operand
lilleman2026-10-05 00:52:59 +02:00
19cbbe56f6
Answer prose round 1: show binding a selected sex, split the test-series paragraph, give the birth-number layout both reasons, and say which item the round leaves
lilleman2026-10-05 00:47:20 +02:00
60b3cb20ca
Answer product-owner round 1: show reading a name and a personnummer through one bound sex, say what the locale address prints, and plan the record's one pick in item 4
lilleman2026-10-05 00:44:17 +02:00
b93d47eeb2
Answer stability round 2: let the selector be the assertion
lilleman2026-10-05 00:44:17 +02:00
38d791d9b1
Re-pin the seeded address examples for the address bound to its locality
lilleman2026-10-05 00:38:21 +02:00
b5be59f180
Re-pin the shape for the address bound to its locality
lilleman2026-10-05 00:38:21 +02:00
1afcbc1a83
Answer stability round 1: bind the locality so population still weighs an address, test the field paths agree, and restate why birth-number sits under sex
lilleman2026-10-05 00:38:20 +02:00
06c17411d6
Document the named person and address picks, revise the address decision, and close item 3
lilleman2026-10-05 00:30:26 +02:00
b17f29f983
Re-pin the seeded address examples
lilleman2026-10-05 00:29:12 +02:00
1cff081f51
Re-pin the shape for the named person and address picks
lilleman2026-10-05 00:28:28 +02:00
4b80460515
Draw a shipped person from one named first name, and an address from one named street
lilleman2026-10-05 00:28:18 +02:00
7fd79bb09c
Test that a shipped person and address each come from one named pick
lilleman2026-10-05 00:26:25 +02:00
f03a0de42c
Answer prose round 2: rewrap the Step up and Linked tables paragraphs
lilleman2026-10-05 00:19:34 +02:00
ec1dcbf9d3
Answer prose round 1: name the parent after .., mark the step down as the one exception to the shared draw, and plainer errors
lilleman2026-10-05 00:18:46 +02:00
406232e8f9
Answer stability round 1 and product-owner round 1: spell .. in the fence's and the link column's advice, take it in struct tags, and show the whole climb
lilleman2026-10-05 00:15:13 +02:00
1551087ddf
Answer architecture round 2: say the suggested path starts at the data root
lilleman2026-10-05 00:09:06 +02:00
1ec2bee098
Answer architecture round 1: share a step down's draw per draw group and pick, own descend's pins, name the spelling to write, and record the .. decision
lilleman2026-10-05 00:05:58 +02:00
4b5506d07b
Document .., drop the step-up decision item 2 replaces, and close item 2
lilleman2026-10-04 23:58:50 +02:00
8b76d51f2c
Step up from a row to the row it links to with ..
lilleman2026-10-04 23:56:45 +02:00
07c66c57fc
Test that .. steps up from a row to the row it links to
lilleman2026-10-04 23:51:10 +02:00
5707c697d8
Answer prose round 3: name the five items the round lets merge
lilleman2026-10-04 23:44:37 +02:00
bad5beb42b
Answer prose round 2: items 4 and 90 remove what the earlier items touch, and the scoring run writes the first scores
lilleman2026-10-04 23:44:12 +02:00
e14c9d0f4c
Answer prose round 1: item 5 scores the restructure, which is the round the comprehension rule lets merge, and item 90 says what internal/ buys
lilleman2026-10-04 23:43:05 +02:00
d160de3ee1
Scrap the flat-package decision, plan item 90's folder restructure before the panel, and suspend scoring until item 5
lilleman2026-10-04 23:41:25 +02:00
f3d0959cae
Answer prose round 3 and product-owner round 3: a module is a Go module or a data folder, a manifest names its fejkdata version, and the Versioning rewrite planned
lilleman2026-10-04 23:01:32 +02:00
b2002bb51d
Answer prose round 2 and product-owner round 2: module explained at first use, the seed as item 89, modules in lockstep, and a second break of New for the date
lilleman2026-10-04 23:00:19 +02:00
9240d90547
Answer prose round 2 and product-owner round 2: flexible and extensible, the date in the seed promise, the custom-CLI builder, and the seed required beside item 77
lilleman2026-10-04 22:30:15 +02:00
eee7572360
Answer prose round 1 and product-owner round 1: modules not packages, goal 13 split, the decisions item 77 ends, and a manifest naming every default it reaches
lilleman2026-10-04 22:10:23 +02:00
90be0ee6d8
Make everything replaceable goal 9, require changing inputs in the library and default them in the CLI, and record item 77's answers
lilleman2026-10-04 22:07:37 +02:00
dc48ae11a5
Answer prose round 2: state the library's required inputs as a step
lilleman2026-10-04 20:29:36 +02:00
f3fcf569ad
Answer prose round 1: say item 26 revises the clock decision, fold the direction into its first step, and leave narrowing and the seed to their own items
lilleman2026-10-04 20:28:50 +02:00
32c1fb6c26
Record the maintainer's input-data direction in item 26, and the age bands that weigh a birthdate
lilleman2026-10-04 20:27:07 +02:00
4bf1ee292a
Answer prose round 3 and product-owner round 2: one reading per step, no birthdate after the given date, and the 12-digit claim scoped to testpersonnummer
lilleman2026-10-04 19:34:40 +02:00
84763399aa
Answer product-owner round 1: plan the + so it ships before 2030, on request and in a data author's own category, and file the 12-digit form
lilleman2026-10-04 19:33:27 +02:00
ef164354ab
Answer prose round 2: state the + for personnummer, as SKV 704 does, and check samordningsnummer when the item is picked
lilleman2026-10-04 19:32:21 +02:00
4a2e161cfc
Answer prose round 1: the + from the year its holder turns 100, in both Swedish ids, from 2030
lilleman2026-10-04 19:31:16 +02:00
61e759a489
Plan item 26 for 0.2.0: the + separator from a date the caller gives, exploring how a render takes input first
lilleman2026-10-04 19:29:32 +02:00
663b20b77a
Answer prose round 2: say which paragraph item 87 splits, in the words it fixes, under goal 11
lilleman2026-10-04 17:47:48 +02:00
1af5abf762
Answer prose round 1: say NANPA may assign the codes, spell the test's exchange in full, and file the record paragraph's split
lilleman2026-10-04 17:46:48 +02:00
965d671707
Re-pin the shape for en_US.phone.exchange
lilleman2026-10-04 17:42:46 +02:00
59e3ebe65d
Answer product-owner round 1: name the field exchange, and say in plain words what phone-exchange draws
lilleman2026-10-04 17:42:46 +02:00
2f712d6ec0
Re-pin the shape for en_US.phone-exchange
lilleman2026-10-04 17:38:02 +02:00
951dd88169
Answer stability round 1: draw the exchange from its own category, en_US.phone-exchange, and file the area list's copy
lilleman2026-10-04 17:38:02 +02:00
563237a45a
Draw a US exchange from NANPA's assignable codes, and strip every imported cell
lilleman2026-10-04 17:33:16 +02:00
7ac8442bcf
Test that a US exchange is an assignable NANP code and that no shipped cell is padded
lilleman2026-10-04 17:31:40 +02:00
5bd022fe89
Spell the exact-version install in full, and say which version to raise
lilleman2026-10-04 17:14:55 +02:00
bded47846d
State the seed exception once, with pin-then-regenerate advice, and word --seed's help as the README's row
lilleman2026-10-04 17:13:33 +02:00
6eb9880a3f
Name the version in every seed promise, and say to regenerate seeded fixtures when it changes
lilleman2026-10-04 17:11:27 +02:00
0bedcd47e2
Say a patch may change what a seed draws, so seeded fixtures pin to one version
lilleman2026-10-04 16:55:57 +02:00
48894a55e8
Give the CLI's --seed row the conditions the library's WithSeed row states
lilleman2026-10-04 12:19:14 +02:00
b2406ef4bc
Answer prose round 3: say where NaN prints, and leave item 77's option name open
lilleman2026-10-04 12:19:06 +02:00
fd313b76b6
Wrap the zero-divisor decision's last lines
lilleman2026-10-04 12:18:01 +02:00
665c532f8c
Answer prose and product-owner round 2: one idea per sentence in items 77 and 81, item 77's open API points, and NaN explained where the decision names it
lilleman2026-10-04 12:17:56 +02:00
fba410c83f
Narrow goal 6.1 to values a template's own rules forbid, and name the data in goal 9
lilleman2026-10-04 12:16:19 +02:00
lilleman
renovate[bot]