-
Notifications
You must be signed in to change notification settings - Fork 3
Fix generator schema row tab order #293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
aee9eeb
Fix generator schema tab order
eviltester 538c995
fixed next release blog post
eviltester aa7450b
Address PR 293 review feedback
eviltester cacd797
Address schema focus review feedback
eviltester 1bf42aa
Merge remote-tracking branch 'origin/master' into codex/271-generator…
eviltester 9c06fd1
Address PR 293 docs and harness feedback
eviltester File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,89 @@ | ||
| --- | ||
| slug: auto-increments-helpers | ||
| authors: [alan] | ||
| tags: [release, feature] | ||
| date: 2026-06-30T10:00 | ||
| --- | ||
|
coderabbitai[bot] marked this conversation as resolved.
|
||
|
|
||
| This release expands the commands available in the domain model, allows more helper functions in the UI and has general UI improvements. | ||
|
|
||
| <!-- truncate --> | ||
|
|
||
| ## 1. Auto-increment timestamps for deterministic event streams | ||
|
|
||
| You can now generate timestamps that move forward one row at a time instead of relying on purely random dates. | ||
|
|
||
| Example: | ||
|
|
||
| ```text | ||
| CreatedAt | ||
| autoIncrement.timestamp(start="2026-06-12T12:39:23Z", step=1, type="seconds") | ||
| ``` | ||
|
|
||
| That produces: | ||
|
|
||
| - row 1: `2026-06-12T12:39:23Z` | ||
| - row 2: `2026-06-12T12:39:24Z` | ||
| - row 3: `2026-06-12T12:39:25Z` | ||
|
|
||
| This is useful for audit logs, event streams, ordered API records, and any test data where time should progress predictably across generated rows. | ||
|
|
||
| Docs: | ||
|
|
||
| - [autoIncrement Domain](/docs/test-data/domain/autoIncrement) | ||
|
|
||
|
|
||
| ## 2. Constraint-aware auto-increment sequences for generated identifiers | ||
|
|
||
| Schemas can now generate sequential IDs through the domain model with `autoIncrement.sequence`. | ||
|
|
||
| Example: | ||
|
|
||
| ```text | ||
| Filename | ||
| autoIncrement.sequence(start=1, step=5, prefix="filename", suffix=".txt", zeropadding=3) | ||
| ``` | ||
|
|
||
| Generated values: | ||
|
|
||
| ```text | ||
| filename001.txt | ||
| filename006.txt | ||
| filename011.txt | ||
| ``` | ||
|
coderabbitai[bot] marked this conversation as resolved.
|
||
|
|
||
| This is especially useful for ticket IDs, filenames, and human-readable references because the sequence only advances when a row is accepted. If a generated row is rejected by constraints and retried, the skipped attempt does not consume the next number. | ||
|
|
||
| Docs: | ||
|
|
||
| - [Auto Increment Sequences](/docs/test-data/auto-increment-sequences) | ||
|
|
||
| ## 3. Allow unsafe Faker helpers from the UI when you trust the schema | ||
|
|
||
| Faker helper commands stay safe by default. Simple literal helper calls continue to work normally, but expression-style helper arguments that execute callback-shaped schema text require an explicit opt-in. | ||
|
|
||
| That opt-in is now available in the Web UI as **allow unsafe faker** in the Test Data Settings dialog behind the cog. | ||
|
|
||
| Example unsafe helper: | ||
|
|
||
| ```text | ||
| Names | ||
| helpers.multiple(() => this.person.firstName(), { count: 3 }) | ||
| ``` | ||
|
|
||
| Use this only for schemas you trust. The browser setting now matches the other integration surfaces: | ||
|
|
||
| - Web UI: enable **allow unsafe faker** from the Test Data Settings cog. | ||
| - REST API: pass `unsafeFakerExpressions: true` in supported generation request bodies. | ||
| - CLI: pass `--unsafe-faker-expressions`. | ||
| - MCP: pass `unsafeFakerExpressions: true` in the generation tool arguments. | ||
|
|
||
| Docs: | ||
|
|
||
| - [Faker Helpers](/docs/test-data/faker/helpers) | ||
| - [Web UI](/docs/interfaces-and-deployment/web-ui) | ||
| - [REST API](/docs/interfaces-and-deployment/rest-api) | ||
| - [MCP](/docs/interfaces-and-deployment/mcp) | ||
| - [CLI](/docs/interfaces-and-deployment/cli-node-and-bun) | ||
|
|
||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At widths 481–980px, the later
@media (max-width: 980px)rules only changegrid-columnfor the row actions and name input and do not resetgrid-row. Because this new base rule pins the actions to row 1 while the new name-input rule also pins the textbox to row 1, the action buttons and column-name field overlap on tablet-width layouts; add responsivegrid-rowoverrides while keeping the desktop left-action column.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implemented in
aa7450b1.The tablet layout now explicitly places the shared schema row actions on grid row 1 and the column-name input on grid row 2 inside the
max-width: 980pxrules, so the desktop left-action-column placement does not carry an overlapping row assignment into tablet widths.Verified with the targeted generator schema-edit Playwright spec,
pnpm run verify:ui,pnpm run verify:local, and the pre-push verification hook.