nushell

mirror of https://github.com/nushell/nushell.git synced 2025-08-04 22:30:31 +02:00

Files

132ikl da9615f971 Fix parse-time pipeline type checking to support multiple output types for same input type (#16111 )

# Description
Fixes #15485

This PR changes pipeline checking to keep track of all possible output
types instead of only first type matching input type which appears in
the input/output types. For example, in this command:
```nushell
def foo []: [int -> string, int -> record] {
  # ...
}
```
An `int` input to the command may result in a string or a record to be
output. Before this PR, Nushell would always assume that an `int` input
would cause a `string` output because it's the first matching
input/output type pair. This would cause issues during type checking
where the parser would incorrectly determine the output type. After this
PR, Nushell considers the command to output either a string or a record.

# User-Facing Changes
* Parse-time pipeline type checking now properly supports commands with
multiple pipeline output types for the same pipeline input type

# Tests + Formatting
Added a couple tests

# After Submitting
N/A

---------

Co-authored-by: Bahex <Bahex@users.noreply.github.com>

2025-08-02 09:35:25 +08:00

src

Fix parse-time pipeline type checking to support multiple output types for same input type (#16111 )

2025-08-02 09:35:25 +08:00

tests

Refactor: introduce 2 associated functions to PipelineData (#16233 )

2025-08-02 09:30:30 +08:00

Cargo.toml

fix(input list): don't leak ansi styling, fuzzy match indicator preserves styles (#16276 )

2025-07-31 22:42:10 +02:00

LICENSE

Fix rest of license year ranges (#8727 )