swarm-ui: try-out rows keyed by position, distinct names, and accurate storage wording
Two classifications sharing a name made the result table's row key collide, so the form now refuses duplicate names and the table keys rows by position anyway. The page said it stores nothing in the browser, but the result table remembers its column filters like every table does; the header comment and the docs now say that. The row cap's comment says to keep it in step with the endpoint's own cap.
This commit is contained in:
parent
b67517e41b
commit
a4a4381cf6
4 changed files with 26 additions and 7 deletions
|
|
@ -64,8 +64,9 @@ and the head commit the run read. A failed run shows its error, for example when
|
|||
has no API key yet.
|
||||
|
||||
What you typed stays after a run, so you can edit the classification and run it
|
||||
again. The page saves nothing and posts nothing to the forge. It shows no token
|
||||
counts, cache counts or cost.
|
||||
again. The page saves no classification and no result, and posts nothing to the
|
||||
forge; like every table in the UI, the result table remembers its column
|
||||
filters in the browser. It shows no token counts, cache counts or cost.
|
||||
|
||||
### Scheduled prompts
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue