Skip to content

Comments

fix: allow filtering on custom named types#212

Merged
ohler55 merged 1 commit intoohler55:developfrom
rdumont:feat/filter-custom-named-types
Aug 16, 2025
Merged

fix: allow filtering on custom named types#212
ohler55 merged 1 commit intoohler55:developfrom
rdumont:feat/filter-custom-named-types

Conversation

@rdumont
Copy link
Contributor

@rdumont rdumont commented Aug 15, 2025

A custom named type being:

type Color string

A filter expression on the value "blue" would work normally, while on the value Color("blue") it would silently never match.

This was unexpected and (as far as I could tell) undocumented behavior, so I decided to fix by supporting custom named types for all common types.

A custom named type being:

```
type Color string
```

A filter expression on the value `"blue"` would work normally,
while on the value `Color("blue")` it would silently never match.

This was unexpected and undocumented behavior, so I decided
to fix by supporting custom named types for all common types.
@ohler55
Copy link
Owner

ohler55 commented Aug 16, 2025

Thank you. A nice improvement.

@ohler55 ohler55 merged commit bd36ceb into ohler55:develop Aug 16, 2025
3 checks passed
@rdumont rdumont deleted the feat/filter-custom-named-types branch August 19, 2025 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants