[2.x] Fix misleading error message when .evaluated is used outside macro context (#8951)

Fixes #1144

The compileTimeOnly message on wrapInitInputTask said "`value` can
only be called on an input task..." when the user called `.evaluated`,
not `.value`. Changed to say `evaluated` and suggest `.toTask(" <args>").value`
as an alternative.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
BrianHotopp 2026-03-21 19:27:53 -04:00 committed by GitHub
parent 7b23ee96d3
commit d1468f414a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions

View File

@ -59,7 +59,7 @@ object InputWrapper:
def `wrapInputTask_\u2603\u2603`[T](@deprecated("unused", "") in: Any): T = implDetailError
@compileTimeOnly(
"`value` can only be called on an input task within a task definition macro, such as := or Def.inputTask."
"`evaluated` can only be called on an input task within a task definition macro, such as := or Def.inputTask. To use an input task from a regular task, use `.toTask(\" <args>\").value` instead."
)
def `wrapInitInputTask_\u2603\u2603`[T](@deprecated("unused", "") in: Any): T = implDetailError