You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the parser understands key value pairs that are not simple equality. For example: [subdir != "win-64] is valid and understood. However, you can't yet do anything with it yet. Lets support this properly and make the matching logic understand it.
[license >= "GPL-3"] # doesn't make sense
[build >= "hdfdf_py39" ] # No way to do greater than on a string like this with out causing surprises
[sha256< "abcdef12345"]
The text was updated successfully, but these errors were encountered:
If we are adding equality checking for things like license and sha256 and the like, does this mean we're going to have to add those attributes to the MatchSpec struct? I've gotten rusty in my Rust, so I apologize if this is an obvious question.
Right now the parser understands key value pairs that are not simple equality. For example:
[subdir != "win-64]
is valid and understood. However, you can't yet do anything with it yet. Lets support this properly and make the matching logic understand it.Examples
Here's some possible sensible use cases:
Here's some that shouldn't work:
The text was updated successfully, but these errors were encountered: