Skip to content

[FEATURE]More comfortable guardrail validation #2177

Closed as not planned
Closed as not planned

Description

@elda27

Feature Area

Core functionality

Is your feature request related to a an existing bug? Please link it here.

Validation of guardrail is inconvenience due to insufficient consideration of use cases.
I can PR in this problem.

I think following use cases makes error now.

  • A function has positional arguments.
  • A new style return annotation such as tuple[bool, Any].
  • Strict typing, tuple[bool, str] or tuple[bool, TaskOutput].

Describe the solution you'd like

Change the validation as strictly.

Describe alternatives you've considered

No response

Additional context

No response

Willingness to Contribute

Yes, I'd be happy to submit a pull request

Activity

  1. added a commit that references this issue on Feb 20, 2025
    3c5672f
  2. github-actions commented on Mar 23, 2025

    @github-actions
    Contributor

    This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

  3. github-actions commented on Mar 28, 2025

    @github-actions
    Contributor

    This issue was closed because it has been stalled for 5 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions