← Back to issue list

`for` grammar: include "any" as an always-on platform

View original Github issue

Metadata

Project
craft-grammar
Number
#122
Type
issue
State
closed
Author
lengau
Labels
Type: Enhancement Status: Triaged
Created
Updated
Closed

Current evaluation

Implemented `any` as an always-on `for` selector via PR #129; application-supplied platform names still reject `any`.

Resolution: closed resolved

Reason: PR #129 implemented the requested always-on selector behavior and closed #122. The processor internally includes `any` while explicitly rejecting it as an application platform name.

Evaluated by: mr-cal-bot

No scores available.

Issue body

For "for" grammar, saying "for any" should be semantically equivalent to an `if True` statement. The application MUST NOT pass "any" as a platform name.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Implemented `any` as an always-on `for` selector via PR #129; application-supplied platform names still reject `any`.
stealth/space-bunny-alpha — closed resolved Implemented `any` as an always-on value in `for` grammar by PR #129, resolving #122.
qwen/qwen3.6-35b-a3b — — The enhancement to support any as an always-on platform in the for grammar was closed without implementation. Synced to an internal Jira ticket, it received no developer response or code changes, indicating the feature was abandoned or deferred.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The for grammar enhancement to treat any as an always-on platform was abandoned. Resolution tracking was transferred to Jira ticket CRAFT-4741. No code changes or merges were applied.
qwen/qwen3.6-35b-a3b — — The enhancement to treat 'any' as an always-on platform in the for grammar was closed without implementation. No code changes or merges were made, indicating the feature was abandoned or deferred.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/craft-grammar#129 (confidence 99%)

    PR #129 is identified as the implementation that resolved the requested `for any` behavior.

Related issues

No related issues found above the similarity threshold.