GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add support for type signatures in CEL environment YAML configuration. by copybara-service[bot] · Pull Request #73 · cel-expr/cel-python

Conversation

@copybara-service

@copybara-service copybara-service Bot commented Jun 5, 2026

Copy link
Copy Markdown

Add support for type signatures in CEL environment YAML configuration.

The env_yaml parser now accepts type signatures for variable types and function overload signatures. The type field can be used instead of type_name for variables, allowing a more compact representation of types, including type parameters and parameterized types. The signature field can be used for function overloads, providing a single string to define the overload's target, arguments, and member status. The return type in function overloads can now also be specified as a type signature string.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@dmitriplotnikov @copybara-github
Add support for type signatures in CEL environment YAML configuration.
06752e1 
The `env_yaml` parser now accepts type signatures for variable types and function overload signatures. The `type` field can be used instead of `type_name` for variables, allowing a more compact representation of types, including type parameters and parameterized types. The `signature` field can be used for function overloads, providing a single string to define the overload's target, arguments, and member status. The `return` type in function overloads can now also be specified as a type signature string.

PiperOrigin-RevId: 925627200
@copybara-service
copybara-service Bot force-pushed the test_925627200 branch from 16dd45d to 06752e1 Compare June 5, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@dmitriplotnikov
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.