feat(job-array-one-based-index): control by filter with element selections (task 7.5)
Filter-based ControlJob validates a bracketed -J value before fetching (400 with the parser's message; unbracketed names, including commands with spaces, unchanged). FetchJobList evaluates bracketed job_name entries through the selection predicates instead of unevaluated compound conditions, so -J 'foo[1]' acts on element 1 of every array named foo and never on ordinary jobs of that name. The most-recent-job rule applies only without an element number and without all-jobs, and treats the element of a one-element array like an ordinary job (isSingleElementArray, a documented approximation). The old index-section parser is deleted. Completes bug-1898 on the owned paths. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
db16b565dd
commit
40917a01f0
5 changed files with 251 additions and 134 deletions
|
|
@ -171,7 +171,7 @@
|
|||
- _Requirements: 5.1, 5.3, 5.4, 8.2, 8.3_
|
||||
- _Depends: 5.4, 7.2_
|
||||
|
||||
- [ ] 7.5 Control jobs by filter with element selections
|
||||
- [x] 7.5 Control jobs by filter with element selections
|
||||
- Validate a bracketed name filter before fetching (unbracketed names, including command-line names with spaces, unchanged), returning 400 with the specific message
|
||||
- Route the filter-based job fetch's bracketed name handling through the name parser and the selection predicates; with its last use gone, delete the old index-section parser
|
||||
- Apply the most-recent-job rule only when the filter has no element number and all-jobs is not set, acting on the newest row alone when it is ordinary or the only stored element of its array
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue