Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make match_type typing more strict in planned maintenance #234

Open
stveit opened this issue May 30, 2024 · 0 comments
Open

Make match_type typing more strict in planned maintenance #234

stveit opened this issue May 30, 2024 · 0 comments
Labels
enhancement New feature or request post-zino2.0 These are features Zino1 does not have, but might be desired later

Comments

@stveit
Copy link
Contributor

stveit commented May 30, 2024

Zino1 seems to play a bit fast and loose with stuff like this, but checks for what values are used can be made more strict than #194 does. The device and portstate pms have a different subset of match types they allow, so for post zino 2.0 this can be made more strict
@stveit stveit added the post-zino2.0 These are features Zino1 does not have, but might be desired later label May 30, 2024
@stveit stveit mentioned this issue May 30, 2024
Merged
@lunkwill42 lunkwill42 added the enhancement New feature or request label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request post-zino2.0 These are features Zino1 does not have, but might be desired later
Projects
Zino 2.1 feature prioritization
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lunkwill42 @stveit